Re^2: CGI for (or against) HttpSession?

the session data is stored in memory in the JVM, so it could be hard to get at directly from perl

Just as I would have guessed. Thanks for confirming that. The notion of saving session data externally (e.g. in a temp file on the server?) seems a bit klunky, but it's worth looking into.

If you don't need much information from the session, writing a webservice type interface to a simple java servlet/jsp page might be easier, though.

Forgive me, but I don't know what you're talking about here. It's true that I only need a few short little strings (user-id, organization, permission-level -- less than 48 bytes altogether), and I don't have any trouble with the jsp stuff per se (our java guy provides a jsp template for static page content); so, what would a "webservice type interface to a simple ... jsp page" consist of? Is it some simple, generic thing in java/jsp, or some simple, generic thing in CGI? (Does this become a non-perl question?)

Comment on Re^2: CGI for (or against) HttpSession?

Replies are listed 'Best First'.
Re^3: CGI for (or against) HttpSession? by Joost (Canon) on Mar 31, 2005 at 08:49 UTC
All I mean with webservice is "a dynamic webpage or appliocation that is written to be used from another program via HTTP". So in this case, basically, a jsp page that returns the data you want in some easy to parse format based (probably) on some query parameters (`data.jsp?gimme=this&gimme=that`). "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply] [d/l]