Sam Joseph wrote:
> Not particularly. I mean most browsers do automatic caching already.
> Although it would be useful to be able to control which pages were
> cached, i.e. to store some cached copies for longer - perhaps the ones
> that are bookmarked. I've always set up the URI data model to have a
> local copy reference.
I'm thinking of something for some time now... like: you ask your node
about something, and get some url. You click on url and get the data.
Then, I ask the same node the same thing and get the same url. If we're
in the same building/city/continent and document resides outside, we
will save some bandwidth if I get the data from proxy. And more
important, I can get the data even if ddos attack destroys
Actually I'm fascinated with possibilites of information travelling
through the net where needed:)
> Assuming that we can get jetty to act as a proxy then there are a lot of
> possibilities, but I'm not even sure if it can be done. I'm gonna give
> it a go and let you know.
Hm afaik http proxy is not a big deal, at least it's well documented.
And about caching proxy, I found some iirc URLCache thing on
alphaworks.ibm.com. I don't like it and it's not free, so I'll have to
write something better:)
Anyway it caches everything retreived via URL.openConnection().
> Sure, although part of the point of this release is that it is not
> dependent on servlets at all
One from my wishlist:)
> Sounds good - if I put the code in CVS, you wanna implement this for me?
Yes, I'll do it probably today.
> Torque has some reasonable documentation . Part 4 "writing a sample
> application" of the tutorial is a good place to start:
Thanks, actually I did read this when you introduced torque, but it was