Subject | Re: [Firebird-Architect] XML |
---|---|
Author | Paul Schmidt |
Post date | 2003-04-17T15:28:53Z |
On April 17, 2003 10:03 am, Jim Starkey wrote:
of UDF functions that call an external XML parser/engine, to do the grunt
work. What are the benefits vs costs of doing it this way instead?
I guess the next step is for someone who wants XML support to do a
cost/benefit analysis and post it (or a link to it) as an RFC, and then the
list can fight it out (kind of like a hockey game).
Go Leafs Go!!!!
Paul S
> At 02:53 PM 4/16/03 -0400, Paul Schmidt wrote:The second question, is could this be done other ways, for example a package
> >That's what Firebird does, it stores data. XML can be, and should be
> > limited to being either a source for data, or a destination for extracted
> > data, in other words your populating an XML document with database data.
> > So the question becomes should that be done within the engine, or within
> > the client, and is the benefit of doing it within the engine worth the
> > cost of doing so.
>
> Well said, sir. That is indeed the question.
>
of UDF functions that call an external XML parser/engine, to do the grunt
work. What are the benefits vs costs of doing it this way instead?
I guess the next step is for someone who wants XML support to do a
cost/benefit analysis and post it (or a link to it) as an RFC, and then the
list can fight it out (kind of like a hockey game).
Go Leafs Go!!!!
Paul S