The browser can cache anything it has. The only issue in this regard is what does it have? It NEVER has a Tile. A tile is, ultimately, a Servlet.
Jack On Wed, 16 Mar 2005 10:06:10 -0500 (EST), Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > You are saying exactly what I thought I always knew (i.e., basic > HTTP!!)... So, just to boil this down for the brains I have to argue with > later... > > Tile contents CANNOT be cached by the browser (except if all tiles are > static, in which case the FINAL document returned to the browser could of > course be cached). > > Would you agree with that? And anyone else reading this? > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > > On Wed, March 16, 2005 10:00 am, Dakota Jack said: > > What is sent from the webserver is just what you see in source code on > > the browser. That "source code" is the code sent from the webserver > > to the browser. The browser also uses plugins to get code and > > resources as indicated from the source code via Flash, java script, > > image processing, etc. Any of these things, since they "belong" to > > the browser, can be cached. The browser has no way of knowing or > > relating to Tiles at all. > > > > Jack > > > > -- > > "You can lead a horse to water but you cannot make it float on its back." > > ~Dakota Jack~ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
