Y
yeah
I've been playing around with <iframe> and applet as options for a
client page to get server info without refreshing the whole web page.
I was pleasantly surprised - but really surprised - to find that when
my applet called back to the server (using URL.getContent and a
BufferedInputReader) I was able to retrieve a previously set session
variable by the same web browser visit.
Using tomcat here for web server and java.
I know Tomcat has several options for transparently supporting session
info. I was being pessimistic however and expecting that the applet
would look like a different browser when it connected and therefore
get a different session context.
Anyway, still reading the jsp spec. Meanwhle, if anybody knows the
specifics of why this works I'd be interested to know.
Also, I'd be interested in any discussion of applet vs <iframe> for
this kind of communication. Experiences, pros/cons. Etc. My feeling so
far is that both options are pretty equal but I'm leaning toward
<iframe> because it's simpler.
client page to get server info without refreshing the whole web page.
I was pleasantly surprised - but really surprised - to find that when
my applet called back to the server (using URL.getContent and a
BufferedInputReader) I was able to retrieve a previously set session
variable by the same web browser visit.
Using tomcat here for web server and java.
I know Tomcat has several options for transparently supporting session
info. I was being pessimistic however and expecting that the applet
would look like a different browser when it connected and therefore
get a different session context.
Anyway, still reading the jsp spec. Meanwhle, if anybody knows the
specifics of why this works I'd be interested to know.
Also, I'd be interested in any discussion of applet vs <iframe> for
this kind of communication. Experiences, pros/cons. Etc. My feeling so
far is that both options are pretty equal but I'm leaning toward
<iframe> because it's simpler.