> >Thus the only way I really see it happening is by creating
> >a servlet that is used to manipulate the servlet session,
> >and making a perl class that will connect to the servlet
> >whenever you want to get/set something in the session. You'd
> >have to proxy the cookie so that you get the right session.
>
> There is another way. Make all the objects on your session use JNI to
> write to some shared memory.
This was the point I was making about how the servlet engine does not even
have to be on the same machine as apache. You can't really write to shared
memory, unless it's distributed memory.
I'm sure there are a million and one ways to skin this cat: setting up an
RMI server on the servlet engine and having perl talk native to it; rewrite
the session class to store it's entries in a database; etc. I just don't see
any generic solution that I would particularly want to do or think that
anyone would really like.
James
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
