Am 08.01.2016 um 01:07 schrieb Stefano Miccoli:
>
> I agree: since owserver is multi-threaded by design there is nothing
> wrong with multiple client tasks/threads accessing it concurrently.
> One should just avoid clogging the server wit an excessive number of
> requests.
>
All is fine as long as you are not insisting on the order in which
requests are served. That is because the owserver protocol is based on
TCP, so the order of requests is only honoured per-socket. As soon there
are multiple sockets, messages stuck in them are handled as the
scheduler decides. And this isn't round-robin and not sorted by arriving
time either. It's a complicated scheme based on throughput.
So if you require to control the order of commands -as with
synchronizing /simultaneous/temperature triggers to readouts of the
chips-, you have to stuff them into the same socket on owserver side.
Kind regards
Jan
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
