[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Early Draft Review: XQuery for Java (JSR 225)

• To: <xml-dev@l...>
• Subject: Re: Early Draft Review: XQuery for Java (JSR 225)
• From: "Ken North" <kennorth@s...>
• Date: Wed, 30 Jun 2004 19:51:27 -0700
• References: <Pine.LNX.4.44L0.0406302026110.4439-100000@s...>

> > 3. Redesigning the API affects the format of the data stream passed between
the
> > XQJ client and the XQuery engine. (disagree here?)
>
> Completely disagree.

Assume postText() is an API we use for HTTP POSTs. Someone decides its more
efficient to use compression instead of sending uncompressed HTML or XML across
the wire. We decide to use LZW compression and replace the postText() String
argument with a binary string or BLOB.

How does that API change not affect the format of the data passed between the
browser (web client) and the web server?

The same priniciple applies for passing queries -- some API changes will alter
the format of the data passed between clients and servers.

• Follow-Ups:
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Rich Salz <rsalz@d...>

• References:
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Rich Salz <rsalz@d...>

• Prev by Date: RE: Early Draft Review: XQuery for Java (JSR 225)
• Next by Date: Re: Early Draft Review: XQuery for Java (JSR 225)
• Previous by thread: Re: Early Draft Review: XQuery for Java (JSR 225)
• Next by thread: Re: Early Draft Review: XQuery for Java (JSR 225)
• Index(es):
  • Date
  • Thread