S Woodside wrote:
Question: What's an "application framework" in the context of this discussion?Could be any hunk of code, really; as long as it can return an XML document to the Provider on demand, it doesn't matter.
I personally favor using something like CGI::XMLApplication because the model fits the way I like to work, but nothing that baroque is required. Again, as long as it can return an XML document to the Provider when needed, it can be as quick-hacky or as over-engineered as the situation warrants.
Just think of the Provider as the bridge between some code that creates an XML document and AxKit.. Make sense?
-kip
simonOn Monday, February 3, 2003, at 11:13 PM, Kip Hampton wrote:Right - it's that App framework that I consider the extra layer. I'm not suggesting that's a bad thing, just a layer I don't have in my systems at the moment.Consider the following: Application Framework (builds XML document) -> Custom Provider -> AxKit
Sure you do. You just use a layer that is implemented soley as a AxKit Language module.(which, incidently, limits you to being able to serve only URIs that have associated files on the disk -- application-based ContentProviders are *not* similarly limited)
If I have an App Provider that accepts data from the client, handles some back-end side effects, and returns dynamic content in response-- how is that more of an "extra layer" than an writing an XSP or XPS document that is handed off to Language processors to do the same things?
--- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
