santuario-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Benito <r...@apache.org>
Subject Re: xmlsec 1.3 released... and now what's left.
Date Sun, 27 Nov 2005 19:51:02 GMT
On 11/26/05, Venu <K.Venugopal@sun.com> wrote:
> Hello Raul,
>
> Raul Benito wrote:
> > Hello Everybody,
> >   After the painful release of the xmlsec(mainly because of the
> > updating of the web page, and deadlines in my "day" job), I begin to
> > wonder where the java xml sec should lead.
> >
> > From my area of expertise, performance:
> >   The fast path (URI selection, only enveloping transformation)  is as
> > fast as it can gets(about 10% overhead of plain serialization and
> > digesting), it can only get better with JCE(70% of execution time)
> > speed ups (Juice any one??).
> >    Anyhow perhaps is time to improve performance in the slow(xpath
> > transformation) path. with a little help we can get rid off the slow
> > circunventbug call.
> >    Or perhaps is better to pursue newer fields, I having playing with
> > SAX and the results are impressive, documents that the DOM library can
> > not ever dream manage the SAX handles without any memory adjustments,
> > and fast as hell.
> >   But SAX is not the api of mode anymore perhaps is better to take a
> > look Stax and begin to work on it. It seems that are more projects
> > using Stax than sax nowadays (axis, xmlbeans,...).
> >
> Are  you suggesting you want to get rid of DOM , can you elaborate a bit
> ?  Canonicalizers are easy to build using StAX writer
> API's.
>

High Venu,

  I'm not suggesting getting rid of the DOM API but I think that there
are domains that will work faster and slimmer with a Stax/SAX API than
with DOM API(WS mainly and perhaps j2me),
  I was suggesting doing something similar to what I suggest in here
http://issues.eu.apache.org/bugzilla/show_bug.cgi?id=32657
   I have blog about my ideas in http://r-bg.com/apache .
   But some other seems to get to the same point as me(It seems after
published after my blogging but I think they gets there indepently, it
is a obvious solution indeed)
http://www.cs.indiana.edu/~welu/c14n_hpdc05.pdf
  So. I think that we shall provides to APIs for the signature
creation/verification (not just c14n) one for trees and other for
streaming.
  What do you all think?


> Regards
> Venu
>
>


--
http://r-bg.com

Mime
View raw message