Lists Home |
Date Index |
- To: Michael Kay <email@example.com>, 'Pete Cordell' <firstname.lastname@example.org>, email@example.com
- Subject: RE: [xml-dev] Another XML parsing idea? Was: Re: [xml-dev] XML Hangover)
- From: Mukul Gandhi <firstname.lastname@example.org>
- Date: Wed, 13 Jul 2005 20:18:15 -0700 (PDT)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=I08mX9bHuOf7r9rwaq2i3a+QF1ydFkT7hRMjQwhaTsQJcUvIkaLGQWDDX0BRO8jlQg1U7VrHv7XtcRZoR/JwBaTMxBGNnVbsbnW1XNiDmG7zvmm/Rg2bOBfUJ53MVIt+mxeq+ZX6QZX2az6rEsci71fY11J6Fr/509OvxaHJESg= ;
--- Michael Kay <email@example.com> wrote:
> A protocol implies sending and receiving messages
> typically across a process
> boundary or even a machine boundary. This would
> raise the cost of XML
> parsing by a couple of orders of magnitude.
I agree, that will be.. Thanks for your thoughts.
> Michael Kay
> > -----Original Message-----
> > From: Mukul Gandhi [mailto:firstname.lastname@example.org]
> > Sent: 13 July 2005 20:01
> > To: Michael Kay; 'Pete Cordell';
> > Subject: [xml-dev] Another XML parsing idea? Was:
> > [xml-dev] XML Hangover)
> > Today, we have a paradigm in XML parsing of using
> > like SAX or DOM. I was thinking of another
> approach to
> > parse XML documents.
> > Can we have a protocol (instead of API) that will
> > between a application and the XML parser? This
> > make using a XML parser interoperable to the
> > application.. We could achieve this "we could have
> > Microsoft XML parser serving Java program's XML
> > parsing request.."
> > Just now we have APIs like SAX and DOM and
> > Microsoft APIs.. Had we had some protocol similar
> > HTTP, that talked between a application and
> parser, it
> > may help interoperability..
> > Is this sensible thinking? Is this idea
> > similar to StAX or .NET XmlReader parsing
> > Regards,
> > Mukul
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around