Yeah, so I keep posting about Coral, I love it. It literally saved me a few hundred dollars in mirror costs, and it's free...so here's a module that would benefit everyone (that doesn't have money for bandwidth) - A module to redirect graphic and static content to the Coral Cache. That would be great as a lot of XOOPS users don't have access to the apache setup on their host. The module could be set up to just serve up files from a certain directory or whatever to the cache, for example all site graphics, or just the most used ones (for a slower site), or even static html pages (that would be really cool, to be able to serve up individual articles from AMS from the cache). I don't know if anyone is going to do it, but I can dream (and teach myself PHP, but that has to wait until this summer).

This would require some serious core hacking, and since XOOPS has it's own caching system, I don't see there is a huge need for this. Sure it can be a nice feature, but with today's hosting offers, bandwidth usually isn't such a big issue anymore.

Just my 2 cents.

Herko

I wouldn't think there would be too much core hacking, but I don't know for sure. It would just have to append .nyud.net:8080 to the url for requests for images (or other multimedia files). So it shouldn't have to interfere with the built in cache. Think of it as more of a redirect type module than a cache.

You may be right about hosting packages, I am just speaking from my experience, especially with larger files like movies and .exe files. For people on a strict budget, those files can kill you, I redirect all of my static content to the cache because I'm a poor college student. Redirecting all of that can be the difference between using a gigabyte a day and 50 MB a day.