Granted. ANYthing that can execute perl code in the context of a request object can do WHATEVER you want, the only question is how easy is it and how reuseable, and how easily can it call on code written by other people that does useful stuff?
I guess what I'm saying is that XSP has a lot of rather useful libraries already. If you do stuff in providers, then you don't have that. Of course you might not need it or whatever. I certainly don't want to dictate how anyone else builds their webapps, I've just found that XSP allows them to be very modular and I think thats a good thing. On Monday 03 February 2003 11:24 pm, Kip Hampton wrote: > Tod Harter wrote: > > <snip/> > > > Granted you could do the same logic > > > > in a provider, but I just see taglibs as being more generic (ie you can > > get your input params from anywhere XSP can get data from whereas a > > provider is really pretty limited in that respect). > > Explain. Any subclass of Apache::AxKit::Provider (which any custom > provider is likely to be) has access to the same request object that the > Language modules have, including XSP.pm. > > Did you not see the apache_request method in there...? > > -kip -- Tod Harter Giant Electronic Brain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
