You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Lavandowska <fl...@yahoo.com> on 2002/02/12 20:07:24 UTC

Re: "dependant" Cache Filter (was [PROPOSAL] commons-filters)

--- bayard@generationjava.com wrote:
> Hey Lance,
<snip>
> ie) readPlant.jsp and readAllPlants.jsp would depend on
> writePlant.jsp. If
> the cache saw a request for writePlant.jsp, it would invalidate
> readPlant.jsp and readAllPlants.jsp. etc etc.

Interesting idea.  Do you have suggestions on how such an organization
would be configured?  Sounds rather messy to be specifying these
"relationships" in web.xml.

> This could then be tied with a servlet that did redirection in a
> configurable way, so that a request could be sent off to another
> site. It

I don't follow this part, why send it off to another site?

Lance

__________________________________________________
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: "dependant" Cache Filter (was [PROPOSAL] commons-filters)

Posted by ba...@generationjava.com.

On Tue, 12 Feb 2002, Lavandowska wrote:

> Interesting idea.  Do you have suggestions on how such an organization
> would be configured?  Sounds rather messy to be specifying these
> "relationships" in web.xml.

Yeah, I've not investigated how you'd specify the dependencies. Maybe the
web.xml would specify a url to find that config xml at or something. Are
there any general patterns for adding new xml config's?

Could a simple rules engine fit?

>
> > This could then be tied with a servlet that did redirection in a
> > configurable way, so that a request could be sent off to another
> > site. It
>
> I don't follow this part, why send it off to another site?

Well, this part of the idea was a follow-on one. It gets into manual
load-balancing a touch, but what if I setup a handful of cache machines,
and then had one real tomcat. I could use the real tomcat for internal
stuff or something, and have all the users hitting the cache machines.

The cache-filter would start to get up into being a web-cache server. So
possibly a bit too far in the future, but the idea seems valid. I'm not
sure if things like squid and the like allow you to build dependency
trees.

Would be interesting to make the dependency concept dynamic, so that
database code/triggers could inform the right webpage etc. I don't know if
that would be considered ugly.

I'm wandering :)

Bay


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>