Re: [bdbxml] input/output event API proposal

Jacoby,

Thanks for the feedback.

Here's another question that is Java-specific.
At this time, the Java versions of these classes use
String as parameters and return values for all of the
methods.  Should all, or some of these use byte[] instead?

Given the tools/application integration that BDB XML Java
users have, which makes more sense?  One or the other,
or a combination (e.g. String for names, but byte[] for
(potentially large) text values)?

Internally, the strings are C++ const unsigned char (UTF-8),
so *some* conversion will happen at the Java interface, and
byte[] may be more efficient, if that matters.

Regards,

George


> I would agree that for a library like DB XML it's more important to  
> have something very close to the native workings than to provide  
> standard interfaces (as you mention).
>
> My main concern about getting docs/elements as strings, then re- 
> parsing them into someplace else is performance and efficiency (and  
> elegance, I suppose), scalability being the prime concern. So being  
> close to native dbxml really knocks that concern on the head.
>
> Also, pull interface for reading is more efficient than a SAX-style  
> push, at this lower level.
>
> That having been said, where I'd first like to use this is as a SAX  
> source & sink for Michael Kay's XSLT 2.0 product (which is a real  
> work of art, I take it EVERYONE is using it!). So for Java it's  
> really a question of producing a SAX converter, which for the basic  
> case looks pretty simple from what you've documented.
>
> Jacoby
>
>
>
> ------------------------------------------
> To remove yourself from this list, send an
> email to [email protected]
>



------------------------------------------
To remove yourself from this list, send an
email to [email protected]