There are no infinite loops in the backend, therefore it will do what
it is requested and terminate. The backend is run every time the
frontend needs the former's services. On every call, the backend
terminates, otherwise we would need some form of messaging between
applications, and probably, fall into traps like requiring the
services of dbus and the like, and we want to avoid that.

Now, in the case of frequently changing wifi hotspots, the frontend
need to be made to detect that a different wifi hotspot is required.
This can be achieved with TTimer calling a subroutine regularly in
which a connection is tested, and in case the active wifi is
unreachable, other wifi's are tried starting with the strongest
signal. In case, no essid file is found, the user is prompted to enter
password and essid. However, this can become a nuisance, so we have to
decide where to stop regarding automating wifi connections.

On 27/08/2015, Steve Litt <slitt@???> wrote:
> On Thu, 27 Aug 2015 08:14:39 +0100
> Edward Bartolo <edbarx@???> wrote:
>
>> I don't think it is necessary to daemonise the backend as connection
>> to and disconnecting from a network is not something that is done
>> continuously.
>
> Unless you're walking down the street in the business district, with
> wifi stations fading in and out.
>
>> Therefore, in my humble opinion, running the backend on
>> request seems to be the best approach. This also avoids additional
>> complexity of requiring a dedicated init script.
>
> I keep forgetting that not everybody runs daemontools or its
> descendents, where "init scripts" are about 6 lines long and there's no
> need for the author of the daemon to make his program go into the
> background.
>
> In other words, I keep forgetting that in sysvinit, systemd, OpenRC and
> the like, daemons have a substantial cost.
>
> Anyway, let me ask you this question: If I were to run the back end on
> a terminal somewhere, would the front end cooperate with it and leave
> it running between front end actions?
>
> I think I'll order a wifi dongle so I can start testing your program.
>
> Thanks,
>
> SteveT
>
> Steve Litt
> August 2015 featured book: Troubleshooting: Just the Facts
> http://www.troubleshooters.com/tjust
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>