Hello Patrick,
the caching of the last server response is pretty generic and should
be available in libsynthesis as far as I remember (no sources here at
1400m in the Swiss mountains :-)
However it's an option and might be disabled or accidentally not
compiled in.
Lukas
l...@synthesis.ch
On 25.02.2010, at 21:18, Patrick Ohly <patrick.o...@intel.com> wrote:
Hello!
How does the server handle message resends by a client? I mean the
situation where a client sends message A, server responds with B, B
gets
lost, clients sends A again after a timeout.
I think Lukas once told me that a server has to remember what data it
received by the client (A) and the reply (B), then when receiving a
message check whether it is the same as A. If so, resend the cached
reply B.
This is something that only makes sense with HTTP. Does that mean that
the implementation of this also has to be in the HTTP server
transport?
Or is there a common implementation of this feature in libsynthesis?
I'm asking because I am running our resend tests against SyncEvolution
as HTTP server and see that tests are failing. Our
syncevo-http-server.py daemon has no special logic for detecting
resends. If the functionality must be implemented there, then this
explains the failure.
--
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
_______________________________________________
os-libsynthesis mailing list
os-libsynthesis@synthesis.ch
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
