Re: Continued development of XMLPull
Stefan Haustein <[email protected]> Fri, 21 May 2004 00:05:47 +0200
| Newsgroups | gmane.text.xml.xmlpull.devel |
|---|---|
| Organization | University of Dortmund |
| Message-ID | <[email protected]> |
Dennis Sosnoski wrote:
> I think these are great ideas. I don't see why they'd be incompatible
> with defining an experimental XMLPull2 interface, though. Even if XPP3
> is the vehicle for testing and refining that interface, it's still good
> to end up with an interface that's separate from the implementation.
Perhaps we can define an interface with additional functionality,
extending XMLPull. The new interface would apply to XPP and wrapper
implementations, but not yet to kXML?
> Even though I'm on a pair of JSR Expert Groups (JAXB 2.0 and JAX-RPC
> 2.0) I've become increasingly skeptical of the whole Soviet-style
> "planned economy" Sun has implemented for Java.
JSR 75 (PDAP) sometimes seemed like a boat where all want to steer and
nobody wants to row. It is simply to stall the process when somebody is
unhappy with a detail. Alternatively, compromises lead to unnecessary
bloat like in the StAX case or spec parts leving everything optional...
Perhaps it would be better if the JCP would only do some
"rubber-stamping", and the actual spec would be designed by
self-organized interest groups...?
> This often seems to lead to specifications that are cumbersome and
> difficult to understand while
> often failing to provide developers with the support they could really
> use. I think open source is a better path for the evolution of Java
> technologies. Seeing what's become of StAX just reinforces that - I
> don't see where it adds anything that's really useful to XMLPull, and it
> actually takes some things away. I recently had it pointed out that it
> doesn't even provide access to the declared namespace stack, for instance.
I think you could generate lots of sad Dilbert comics from real JCP
examples... :(
> Are there any plans to add CharSequence to the mobile platform? I'd
> think that the ability to dramatically reduce the garbage generation in
> a parse would be even more valuable on mobile systems than on standard
> ones. That might justify eventually supporting this in kXML as well as
> XPP3. Meanwhile, an XPP3 implementation could also make use of the NIO
> code for even better performance, since that goes hand-in-hand with
> CharSequence.
I am not aware of any such plans.
Best regards,
Stefan
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/2U_rlB/TM
---------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/xmlpull-dev/
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/