-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tsirkin,
On 2/24/2010 2:21 AM, Tsirkin Evgeny wrote: > On Tue, Feb 23, 2010 at 11:50 PM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----->> What's "flow-resuming" is ?How a >> request can be "resumed" ?Doesn't this goes >>>> againt the idea >>>> of "http is staitless" ,that's vrey interesting? >> >> > So,the "flow-resuming" you were talking about is just the mechanism of > storing the > request parameters and url and use them again after successful > authentication,right? It also stores POST message bodies up to a certain size. > Yes,this probably would not work with custom session ,since tomcat probably > stores the parameters and url in session. Tomcat definitely does, under the session "note", which is a Tomcat-specific implementation detail. > For this particular issue however i have implemented my own mechanism > using custom cookies (server side cookies). Server-side cookies? Sounds like a winner. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuFRPIACgkQ9CaO5/Lv0PBRhgCgwCBL4uSvYBN2epjoLJormtWH YOMAoL47gA31p86jAYmvklsoCb9mQfGe =bL2J -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
