Use of Bluetooth to test programs.

Owen Thomas owen.paul.thomas at gmail.com
Wed Aug 21 09:35:36 UTC 2019


On Wed, 21 Aug 2019 at 18:15, Gilles Gravier <ggravier at fsfe.org> wrote:

> Hello!
>
> Le mer. 21 août 2019 à 09:47, Owen Thomas <owen.paul.thomas at gmail.com> a
> écrit :
>
>>
>>
>> Something else has occurred to me.
>>
>> Part of my test/demo environment will involve shutting down (closing the
>> lid on) both computers, and then opening them up again to see the programs
>> resume their place in the conversation.
>>
>> Would shutting down the hotspot computer cause any consternation for the
>> other computer? If I'm using more than two, shutting down the hotspot will
>> obviously cause the other computers to stop talking, so if I'm going to
>> demo with more than two computers, I'd have reserve a fourth for the
>> hotspot.
>>
>> Is Bluetooth a more appropriate solution or is Bluetooth simply not
>> viable for what I'm trying to do?
>>
>>
>>
> You should configure in the power management options that the device not
> go to sleep when screen is closed...
>

Naah... the computers are supposed to shut down; the whole point of the
environment is to simulate a peer cluster where the participating devices
are not always able to sustain constant connection. The instances of the
program running on each device are supposed to re-engage in this
environment.

I've been running instances of my program on a single computer while I
develop the mechanism that mediates re-engagement. This is kind of a
graduation for the mechanism that has demonstrated efficacy when instances
have been run as multiple processes on a single machine.

-- 
I cut code at an intensity and from a place of my own choosing.
Clique Space(TM). Anima ex machina.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20190821/e9acd4c3/attachment.html>


More information about the ubuntu-users mailing list