-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yves,
On 7/14/2009 2:33 PM, Yves Glodt wrote: > The reason I wanted to manipulate one HttpSession from another is > since in this case, I have an external entity (and thus in another > HttpSession) making a POST request to my servlet, posting information > about a transaction made in another user-HttpSession. > > Manipulating the user-HttpSession from the external request would > have been a way to feed the information from the external entity to > the user-session which is concerned. > > Although I cannot consider this behaviour really beautiful, it's > also not that ugly... > > Or do you (now "you" as "one") disagree or know a nicer way? :-) I'm not sure I really understand what you're doing. You want to accept a POST request from a separately-authenticated user and then publish some data directly into the session of another authenticated user? I'm afraid I can't understand a use case where that makes sense. What if the target session doesn't exist? Is the POSTed information lost? Why not put this kind of information in a database where it can be retrieved by whomever wants it? Or, better yet, build a small pub/sub infrastructure where users (or sessions) register themselves as consumers of POST events. When a POST event arrives, you simply publish it to the group, and those interested in hearing the message will get it and then do whatever they want (such as setting an attribute in the session). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkpc0ioACgkQ9CaO5/Lv0PDa5wCgwrtUmdNxDkpXPiTNjojAVCUZ wrAAoJiR+7varN8AM5UqnSHPaDvIEdo1 =nvTd -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
