Thanks nic
I am trying to create a caching system. I did send another post earlier
about a caching system. An you suggested the getlastmodified() approach. I
looked at this with Jason Hunters implementation available at
www.servlets.com.
I have also looked at cocoon, turbine and also jetspeed and also proxy
servers eg squid.
None of these i have looked into in major depth yet. I just want to get a
list of options available for a caching system.
My main requirements are fine grained control over the caching mechanism.
For example:
if i have cached the request for
www.host.com/products/product_browse.jsp?cat_id=123
then i need to be able to refresh just that cache and nothing else rather
than refreshing all calls matching
"www.host.com/products/product_browse.jsp" regardless of the value of cat_id
like some cach system provide. I need fine grain control.
I also need to still be able log information that is in the HTML file. I
have posted my problem all over the web and now through my own thoughts and
some valuable input from you guys (thanks nic) i am starting to come up with
a solid solution. Once i have tested it will will post it on the design
patterns of www.theserverside.com
cheers.
-----Original Message-----
From: Nic Ferrier [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 17, 2000 5:39 PM
To: [EMAIL PROTECTED]
Subject: Re: Eloquent way to capture the output from a servlet from
inside another servlet
>>> Peter Delahunty <[EMAIL PROTECTED]>
17-Aug-00 5:04:18 PM >>>
>I think this is a "shit" way of doing things so i challenge
>anyone here to come up with a better solution using servlets.
>The problem is servlets do not handle piping in the current
>spec !!!
See the latest draft spec.
http://java.sun.com/aboutJava/communityprocess/review.html
But the servlet API is unlikely to ever do precisely what you want to
do - it is request/response based and thus the chain is one whereby
the last link in the chain issues the response for all other members
of the chain.
With *some* servlet engines you could overload the ServletResponse
object that you pass to the RequestDispatcher to return a caching
PrintWriter in the call to response.getWriter() but that seems an
awfull waste of effort.
Why on earth do you want to do this?
There are alternative systems around, based on top of servlets, that
allow you to do this sort of thing.
See the Apache projects: Coccoon and Turbine.
Nic Ferrier
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
