What you describe (0-size payload message followed by another valid message)
cannot happen.
May be what you really mean is a -1 size payload message? This is a “ping”
which owserver sends every 1 second or so when it is still gathering data or
under heavy payload.
This is an aspect of the owserver protocol which easily gets unnoticed by
implementers: please see https://github.com/miccoli/pyownet/pull/1
<https://github.com/miccoli/pyownet/pull/1> where Johan Ström corrected a
similar bug in my pyownet.
S.
> On 5 Mar 2017, at 17:51, Colin Law <clan...@gmail.com> wrote:
>
> I am trying to debug a problem on the node.js owserver client
> node-owfs and am looking for some clarification of the owserver
> protocol if possible please.
>
> Referring to [1] in response to a 1-wire read I expect to see a header
> with a payload of the size indicated in the header. Very often what I
> actually see is a header specifying a payload size of 0 followed by
> another header with the expected payload size and valid data. Is that
> normal or is there something strange going on?
>
> This is owserver 3.1p4-1 from the raspbian jessie testing repository
> on a pi zero.
>
> [1] http://owfs.org/index.php?page=owserver-protocol
>
> Colin
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
