Hi list!My preferred way of thinking of it is to write a provider when the URL represents the resource you're trying to get at. e.g. if the URL points to a POD document, then the provider is the right thing. If the URL points to a particular entry in your database, then it might be the right thing (distinguish between the database containing the resource and the the database containing a bunch of data you want to search on). Basically, you need to follow the well practiced concept of what goes at the end of a URL.
I've read quite a lot of docs now, but I feel I have not really gained a
good overview yet.
- Provider: Riccardo's HOWTO was nice, but leaves me with a couple of
questions: When is writing a custom Provider going to be the Right Tool
for the Job[tm], as opposed to just writing a taglib to retrieve the
contents? Where does the Provider fit in the pipelines? Must it always
return XML?
On the other hand, there's no hard and fast rule. Technically you can make it look like a URL with XSP (e.g. the AxKit wiki uses XSP, but it's all just plain URLs, no querystrings), so do that if you want to and it makes sense. The reason I chose XSP for the wiki is that it's just plain easier to develop for. You can make changes and have them take effect without having to restart your server (well, you may have to restart, or use Apache::Reload with taglib modules). Plus I find writing taglibs easier than writing providers.
AxKit punts all of that stuff to Apache. Thats why I think Cocoon doing all that stuff is a huge mistake - it merely adds confusing layers onto an already capable system.- Having read tons of Cocoon-docs before seeking refuge here, it would have been cool to see some docs that explains how some Cocoon concepts work in AxKit for people having been in the same situation. Specifically, what I'm looking at is content aggregation and URL matching (that ability to decouple the URL space from the filesystem was pretty neat). I guess the latter could be done by mod_rewrite, but it would be nice to have some easier way, is there?
No, there isn't. I guess partly because the concepts themselves are pretty straightforward - if you can write a perl module you can write a taglib.- Is there some docs on the Auth taglib besides the POD and http://xml.sergeant.org/axkit/xsp/showsource.xsp?auth.xsp
However if you want, feel free to add docs to the wiki :-)
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
