At the risk of sounding like a record-skipping fanboy, SAWA would make a great framework for creating providers in. If you don't like the complexity of such a framework, then plain providers would still be quite an improvement.
Wow, seems like a lot of anti-taglib sentiment out there... :) I think I agree, but I honestly haven't ever messed with providers in AxKit -- the main project I'm using AxKit for was already well underway when I inherited it, and pretty entrenched with the taglib scheme. In coming up to speed on AxKit I was intrigued by providers and the simplicity / power they seemed to offer, but I never had a chance to build anything with them.
Well, I don't think its anti-taglib sentiment as much as it is pro-provider cheering. Taglibs definitely have their place, and IMHO can be a much more powerful mechanism for developing web applications than conventional PHP or ASP code can. However, Providers are just so much more powerful than Taglibs that I shudder at the thought that I might one day have to go back to using PHP.
I feel that XSP+Taglibs allow you to leap into building a web application faster than providers, especially if you don't quite grok AxKit in the first place. But, in my experience, using providers lets you go much farther with your web application without bitrot seeping in.
-- Michael A. Nachbaur <[EMAIL PROTECTED]> http://nachbaur.com/pgpkey.asc
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
