[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)
Ken North wrote, > 1. Burak Emir proposed an API re-design to use an abstract > representation of queries instead of using XQuery strings. So far > we're in agreement. Yes. > 2. He discussed an approach of parsing queries to produce an abstract > syntax tree, serializing that, and passing it to the XQJ driver. > (disagree here?) Disagree. The API would embody the abstract syntax tree directly (for an overly generic comparison, consider the DOM). Passing such abstract queries to an XQJ driver might involve serializing them, but the API need not determine the form ... serialization as XQuery strings would be a straightforward option. > 3. Redesigning the API affects the format of the data stream passed > between the XQJ client and the XQuery engine. (disagree here?) Disagree (for the most part). Whilst there are cases where API design can interact awkwardly with underlying representations (more generally, interfaces can interact awkwardly with implementations) I don't see how that could apply in this case. Cheers, Miles
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|