On Thu, 2009-10-08 at 08:06 +0100, Lukas Zeller wrote: > 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.
It's a safe-guard against parallel data modifications. We can certainly relax it, but then we have to start thinking about sharing all kinds of resources between sessions (directories, data, ...). Doable, but I would have preferred to avoid it. -- 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 [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
