Matt Sergeant wrote:
I second that. A provider is imho the way to go when and only when you will be treating generic non-XML resources (eg mailboxes) as if they were XML while they have document-like semantics, and a less interesting solution when you want to make something that isn't XML look like it is, even though the semantics of both sides differ widely and especially if the non-XML bits are in no way document-alike (eg a DB and lots of that horrible thing called SQL). But of course, you have to balance that with which you are most comfortable implementing and using within your particular context.On Monday, Dec 16, 2002, at 18:51 Europe/London, Sean Evans wrote:Hi, I'm a newbie still trying to wrap my head around when and why it wouldI think it's almost always more desirable to write a taglib. It's just plain easier.
be
desirable to use a taglib over a Provider.
--
Robin Berjon <[EMAIL PROTECTED]>
Research Engineer, Expway http://expway.fr/
7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
