Lance, I'm not as concerned with the location on disk as I am with the actual URL. The goal is to maintain the same URL pattern on the browser but use instead a static version on disk. This is where RewriteRules come in, but then we would depend on Apache. I think that if we can make this optional, it would be great if we can pull this off. Alternatively, we could explore OSCache disk-based caching so we don't have to maintain an entire user's blog on memory. Also, I repeat, I rather have Apache go straight to a static file, than the J2EE container being hit just to read a file from disk.
I'll try to prototype this when I get a chance if you guys tell me you'd be interested in incorporating it. Elias On 8/16/05, Lance Lavandowska <[EMAIL PROTECTED]> wrote: > On 8/16/05, Elias Torres <[EMAIL PROTECTED]> wrote: > > Then we could write RewriteRules in Apache that translated these for > > example: > > > > http://www.jroller.com/page/fate/Weblog?catname=General into > > http://www.jroller.com/static-content/fate/general/index.html > > Suggestion: write the static version to the user's resource directory: > http://www.jroller.com/resources/fate/general/index.html > > The only problem with this is that it could interfere with the > maxDirectorySize admin value (eating up space valuable to the user, so > that they cannot upload a file). Since currently that value only > measures against the "base" resource directory for the user > (/resources/fate) we can get aroudn this issue for the time being by > writing all static content to a subdirectory. THis stops working > if/when we allow the user to create subdirectories. > > Lance >
