You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Thorsten Scherler (JIRA)" <ji...@apache.org> on 2009/01/02 21:21:44 UTC
[jira] Updated: (COCOON3-12) StAX research
[ https://issues.apache.org/jira/browse/COCOON3-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thorsten Scherler updated COCOON3-12:
-------------------------------------
Attachment: Stax_Analysis.pdf
The file the original mail had attached
> StAX research
> -------------
>
> Key: COCOON3-12
> URL: https://issues.apache.org/jira/browse/COCOON3-12
> Project: Cocoon 3
> Issue Type: Improvement
> Components: cocoon-pipeline
> Reporter: Thorsten Scherler
> Assignee: Cocoon Developers Team
> Priority: Trivial
> Attachments: Stax_Analysis.pdf
>
>
> http://marc.info/?t=123011253400002&r=1&w=2
> An evaluation of the latest XML processing technologies regarding their
> usability in Cocoon3 (especially if there are suited to be used in a
> streaming pipeline).
> As it's commonly know we decided to use StAX as our weapon of choice to
> do the XML, but this paper should explain the whys and hows and
> especially the way we took to come to our decision, which resulted in
> using the very same API.
> Eleven pages should be a to big read and it contains all necessary links
> to all the APIs we evaluated and also line wise our two cents about the
> API we observed. Concludingly we also tried to show the difference
> between the currently used SAX and the of us proposed StAX API.
> I hope this work sheds some light on our decision making and taking and
> that someone dares to read it.
> posted by Michael Seydl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.