Zitat von Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>:
On Thu, Oct 6, 2011 at 10:44 AM, Hendrik Sattler
<post@xxxxxxxxxxxxxxxxxx> wrote:
The order is correct. Actually, with openobex-1.5 it may happen that you see
one OBEX_EV_STREAMAVAIL before OBEX_EV_REQCHECK if a BODY header is included
in the first packet, and no OBEX_EV_REQCHECK if the PUT has only one packet.
However, for current git (if a new version is ever going to be released),
this order is strictly correct if the request is not aborted before being
complete.
Yep, so obexd is broken for quite some time, since we do check also on
OBEX_EV_REQ, but the documentation is not very clear about it since it
says:
/* An incoming request has arrived */
Also it doesn't help that OpenOBEX has tree events with similar
interpretation and probably because REQCHECK is not always generate we
had to have a proper check also on REQ too.
Ask Marcel why there is no new release of OpenOBEX! This could have
been fixed for months.
Well I guess this is another reason to move on and start porting the server
side to gobex which is much more mainloop friendly and less confusing is this
aspect.
s/mainloop/glib/
HS
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
