I'm pondering about the design of a website that I'm developing, and
before I found AxKit I was thinking of making a framework sort of like
http://www.perlmonks.org, with a single index.pl that takes some form of
request string to specify the page that you want to view.
So now that I've found AxKit and am starting to feel somehwat
comfortable with it, I'm wondering if something like this is possible:
- all access go through a single URL.
- that script or whatever fetches/finds the XML page content to be
used by AxKit
( presumably the content will reside on disk as a file )
- Let AxKit do its thing, and deliver the page to the browser.
Now, while I'm not even close to being an expert on mod_perl and Apache
server side programming in general, I think the above is feasible.
But what I am not sure about is if the above sequence of things would
prohibit AxKit from performing certain tasks that it would normally do
when content is accessed directly, like caching of transformed contents?
Is there other issues with this approach?
Any comments appreciated.
Also, if this whole approach sounds stupid, please do let me know...:)
thanks in advance,
--d
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
