Am Donnerstag, 23. Juni 2011, 10:31:26 schrieb Luiz Augusto von Dentz: > I guess he meant that to make this work properly the socket must be > non-blocking so that OpenOBEX needs to detected when a packet could > not be written and somehow wake-up the application whenever it can > resume. I mean that currently OpenOBEX uses non-blocking sockets like blocking socket by busy-looping until all data of one packet is written. On slow devices, this is maybe not wanted, especially when using non-blocking sockets in the first place :) The control of re-calling OpenOBEX is still on the application side. 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
