Hi, Thanks for all the advices. My problem is a little bit tricky than that. Some of my clients aren't browser at all (i.e. we built command line tool dedicated to this task which gives us more flexibility than a browser). Thus, adding cookies is out of our actual scope. Maybe "remote port" will do the job.
cheers Y. ----Message d'origine---- >Date: Thu, 13 Mar 2008 07:49:31 +0200 >De: "Robert Iakobashvili" >A: "Niels Provos" >Sujet: Re: [Libevent-users] sockets descriptor access >Copie à: Ycrux, "Lyes Amazouz", > libevent-users@monkey.org > boundary="----=_Part_15007_4546264.1205387371838" > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > >Hi Neils and Ycrux, > >On Thu, Mar 13, 2008 at 6:44 AM, Niels Provos <[EMAIL PROTECTED]> wrote: > >> On Wed, Mar 12, 2008 at 2:40 PM, Ycrux <[EMAIL PROTECTED]> wrote: >> > We can have the case that multiple clients use the same IP address. >> > Hashing this IP will produce the same digest. >> >> The way that this is done usually with HTTP is to set a session cookie >> on the client. The client then echos the cookie back and everything >> is good. > > >Yes, it works. However, when several FireFox browsers are running at the >same host >or tabs within the same FF or tabs within IE-7,8, they will all share the >same cookie, >that may be an issue to handle. > >Sincerely, >Robert Iakobashvili >"Light will come from Jerusalem" >........................................................... >http://curl-loader.sourceforge.net >An open-source web testing and traffic generation. > > _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listinfo/libevent-users
