[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: Burak Emir <Burak.Emir@e...>
• Date: Tue, 29 Jun 2004 10:41:49 +0200
• Cc: xml-dev@l...
• In-reply-to: <006e01c45d53$fdf92990$1601a8c0@DURANTE>
• References: <20040620080246.RJLE21846.mta08-svc.ntlworld.com@Turtle> <40D6D10F.8010705@e...> <40D720B2.7050004@o...> <200406212058.19416.miles@m...> <006e01c45d53$fdf92990$1601a8c0@DURANTE>
• User-agent: Mozilla Thunderbird 0.5 (X11/20040208)

Ken,

Ken North wrote:

>If we pass strings between XQJ clients and XQuery servers, developers who've
>been processing SQL using C++, PHP, Perl, and Python will often choose to
>support XQuery by adapting existing scripts or classes.
>
>  
>
What do you mean by XQJ client ? Is it the driver, which implements the 
XQJ API, takes the queries and sends them off to the server ?
Or do you mean the code written by the XQJ user ?

I think the user should be able to choose what to pass to the XQJ driver 
(or client) - be it strings for compatibility, or trees for sanity reasons.

The driver can then do fancy things in its executeUpdate or executeQuery 
implementation which should not be of concern to the user.

>On the other hand, if an XQJ client must emit abstract syntax trees (serialized
>as Java byte arrays), we'll have to write Java programs for both ends of the XQJ
>client - XQuery server link.
>
>  
>
But that is an implementation choice that is well beyond the scope of 
the XQJ spec, isn't it ?

I am not sure whether one would always choose to transmit the AST, 
because drivers may choose to create something more low-lever than that 
(s.th. closer to "execution plans"). But I am sure that what ever you 
want to transmit, you can generate it nicely from the AST.

Any Java byte arrays can be "serialized" to a sequence of bytes (just 
don't call the "serialize" method, but write something like 
"toMyCustomBLOB()").

cheers,
B.

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

• References:
  • RE: Early Draft Review: XQuery for Java (JSR 225)
    • From: "Michael Kay" <michael.h.kay@n...>
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Burak Emir <Burak.Emir@e...>
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Bob Foster <bob@o...>
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Miles Sabin <miles@m...>
  • 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)
• Next by Date: Re: How It All Goes Wrong (WAS RE: Triplets onthe Internet)
• 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