[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: Ken North <kennorth@s...>
• Subject: Re: Early Draft Review: XQuery for Java (JSR 225)
• From: Rich Salz <rsalz@d...>
• Date: Wed, 30 Jun 2004 22:54:01 -0400 (EDT)
• Cc: "xml-dev@l..." <xml-dev@l...>
• In-reply-to: <000501c45f16$54f3ce80$1601a8c0@DURANTE>

> 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 API implementation can then uncompress.  In this example it's kinda
silly, but  there is no *requirements* that an API expose wire protocol
details.  In fact, if done right, it probably shouldn't.
	/r$
 --
Rich Salz                  Chief Security Architect
DataPower Technology       http://www.datapower.com
XS40 XML Security Gateway  http://www.datapower.com/products/xs40.html
XML Security Overview      http://www.datapower.com/xmldev/xmlsecurity.html

• References:
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: "Ken North" <kennorth@s...>

• Prev 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