At 01:23 PM 07/02/2002 -0700, Owen Stenseth wrote: >How is this any different than applying multiple output styles? I >thought a provider was the initial source for a document. > >What exactly is a POD provider? or a HTML provider? I thought those were >output transformations not data sources.
Right. Exactly. What he means, though, I think, is: let's say you are using the new Provider::PodSAX module (which uses a SAX Driver for POD files on the disk) and you also want to store your POD docs in a DB. In that case, you'd have to have two more-or-less identical Providers (on that's a SAX driver for files on the disk and the other for data coming from the DB). IMO, "stackable providers" (though that's a bit of a misnomer) would likely add complexity to AxKit while only arguably adding value for very specific cases. That is, there's nothing stopping you from getting the same net result now, and "i want to provide content from different sources but i only want to use one Provider" seems like a pretty artificial requirement. For example, in the case above, the custom Provider could just be extended to handle disk vs. DB data sources via a little coding an custom config directive. .02USD, YMWV, -kip Kip Hampton Perl and XML: http://xml.com/pub/q/perlxml AxKit: http://axkit.org/ Join Us In San Diego! http://conferences.oreillynet.com/os2002/ http://conferences.oreillynet.com/cs/os2002/view/e_sess/2533 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
