I am certain on this one, because you can do this sort of thing *without* the web or app servers at all. I do this fairly frequently with code not unlike and heavily borrowing in principle from Jason Hunters HttpMessage and HttpsMessage in COS. The ResourceAction sends the response and ends the whole process by returning null.
I agree, obviously you can take Tomcat for instance and use it to serve everything... I have a production app that is a single server running Tomcat and Oracle and that's it, no web server anywhere, everything is served from Tomcat whether it's a JSP, an image, an HTML document or whatever else.
The question that's in my mind though is what happens when you have a web server in front of Tomcat? Just "rendering to the response" in a servlet might not be enough in that case... Think of a proxy analogy... Does the web server almost appear like a proxy? In other words, a request comes in to the web server, does it (a) pass the connection to the app server to fulfill, at which point it's done and can service more requests, or (b) does it ask the app server for the resource, whatever it is, wait for the response from the app server and send it along to the client when the app server is done responding? Same idea as a network proxy.
The point being, just because the app server CAN serve everything, doesn't necasserily mean it WILL with a web server in front.
But again, I don't know the answer here, it's just a question in my mind.
ceteris paribus
</snip>
Heh, I meant to tell you last time, this is Latin, not Greek. LOL ///;-)
Really?? Well, I have something to yell at my Macroeconomics professor for then! I know for sure she said it was Greek! :)
Funny aside... My Macroeconomics professor... her last name, and I couldn't have made this up, is Economopolous. That just rules!
But now your pushing those caching decisions back on the browser, right? I thought one of your basic premises was to not trust the browser to construct URLs and such? Wouldn't you have the same distrust for caching? (and probably worse since that is at least at the users' discrection)
</snip>
The answers are no, yes, no. Setting caching in the response object is not equivalent to setting caching in the <meta> tags. This is why the ResourceAction has an edge. Note also that the setting of cache, pragma and expires are runtime alterable, and can override the <meta> tags, in ResourceAction. I left those decisions out of the code I sent you. Did you notice where I added in it response to someone's query on that?
I did notice, but my point is that the browser settings would override any tags or headers you set. I might be wrong about that, but that would be my expectation. After all, what good is a setting in my browser that says don't cache anything if a web site designer can come along and overrule that? Surely the FOSS community would be up in arms over their loss of freedom, right?!? ;)
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
