http://bugzilla.moblin.org/show_bug.cgi?id=6175
--- Comment #7 from pohly <[email protected]> 2010-03-11 05:36:15 PST --- (In reply to comment #6) > > I don't know what the effect of not using the suggested session ID is. I > > marked > > it as a TODO because I saw that the SAN message contains it. Some servers > > might > > depend on it. > Checking the spec, I don't think session ID was meant to be used like this. > The > ID is actually used to help the client to identify the same SAN requests from > a > server (As the server might sent multiple SAN continuously) and thus only need > to respond to one of the requests. > Again this is not true for SyncEvolution Server at this moment, on the server > side we might first ensure the generated session ID need to be unique. > > On the clietn side, I think we can implement like this: > If the SAN request with the same session ID was received within a reasonable > time period (say 1 hour), we should ignore this packet. I don't think we need to worry about the session ID right now when it is only meant for detecting SAN resends. That may be necessary when it is sent via a link with packet loss, but via Bluetooth, the message will be received exactly once and only be resent when explicitly requested. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
