Hello! As discussed here in an earlier thread, when clients don't get a reply to their HTTP POST, they can resend that message and that way work around half-open TCP connections. It may also be a good idea in case of other, detected network problems.
Over on the SyncEvolution list we we are now discussing the integration of SyncML with OBEX as part of a Linux desktop. Here the question of message resending came up again. With HTTP, clients can be redirected to a special URL which encodes a session ID. That means messages resent after a loss of connection can still be matched with the session before parsing the message content. With OBEX connections, the same thing is not possible: it is not possible to include meta information when reconnecting, so the SyncML recipient would have to parse the message before it can determine the session ID. The other problem is the question who reconnects. In the normal OBEX use case, the desktop runs as SyncML server and connects to the client. But the current "resend message by client" error handling would then depend on the client being able to connect to the server. Finally, OBEX would work over USB, Bluetooth and IrMC. A server which has connected via Bluetooth might come back via USB. I remember that Lukas mentioned experiments where devices were disconnected while a session ran and it continued seamlessly after reconnecting. Was that using HTTP as transport protocol or OBEX? If it was HTTP, any thoughts on doing the same with OBEX? Hopeless or doable? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ os-libsynthesis mailing list os-libsynthesis@synthesis.ch http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
