On Monday, Feb 3, 2003, at 19:09 Europe/London, Kip Hampton wrote:
Matt Sergeant wrote:
It's one way to do it. I personally haven't used the provider method
(see
the Wiki for how I did it), because I feel it lacks flexibility.
Given that a Provider has access to everything that is available for
the Language modules *and* gets to control both the content and the
styles that are applied, how does it lack flexibilty, exactly?
Simply because the Providers are read only at the moment, so there's no
direct method for submitting changes back - you need an extra
application layer *somewhere*.
It was
originally meant as a publishing layer, and I'm not entirely sure it's
powerful enough for building web apps
Oh? My experience is quite different...
Consider the following:
Application Framework (builds XML document) -> Custom Provider -> AxKit
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.
In practice, this allows Perl developers to do what they want, how
they want to do it as long as the proper XML content is returned from
their application, while still taking advantage of the seperation of
concerns and other more obviously practical benefits that AxKit > offers.
Try it sometime, you'll *really* like it :-)
You're probably right ;-)
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
