Hi Patrick,
On Oct 8, 2009, at 8:51 , Patrick Ohly wrote:
On Wed, 2009-10-07 at 15:36 +0100, Lukas Zeller wrote:
On Oct 7, 2009, at 13:36 , Patrick Ohly wrote:
On Wed, 2009-10-07 at 11:11 +0100, Lukas Zeller wrote:
On Oct 1, 2009, at 15:26 , Patrick Ohly wrote:
The problem is recognizing that the new session is from the same
client.
Same IP address (for HTTP) doesn't mean same client (= Device ID),
for
example in a multi-user systems.
Why bother at all - as long as you can figure out if it's a new
session or not that is enough - timeout will clean up orphaned
sessions no matter from what device.
Except that we currently cannot start the new session before the old
one
expires. Asking the client to wait 5 minutes before his next
authentication request is not a solution, I'm afraid ;-}
Certainly not. I didn't understand that you *can't* run more than one
session, I just thought that was a limitiation of the first test setup.
I was hoping to solve this by terminating sessions of identical
clients,
but it seems that I really need at least some overlap between sessions
even for that.
If you can manage another login attempt with a session still open, you
can run the new session until the header is parsed and then abort the
previous session based on "initialLocalURI" (see other mail) before
continuing the new one to the point where it starts accessing the
datastores.
Best Regards,
Lukas Zeller ([email protected])
-
Synthesis AG, SyncML Solutions & Sustainable Software Concepts
[email protected], http://www.synthesis.ch
_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
