On Wednesday 28 April 2010 11:24:25 am Colm O hEigeartaigh wrote: > 1.5.9 may be faster than 1.5.8 for signature processing due to these two > fixes: > > https://issues.apache.org/jira/browse/WSS-214 > https://issues.apache.org/jira/browse/WSS-215
Oh. Cool. Can we get 1.5.9 out soon? :-) > > If I find the time I might consider going through the work I did on trunk > on improving the signature and encryption processors to see if it's worth > backporting some of it, e.g.: > > https://issues.apache.org/jira/browse/WSS-171 > https://issues.apache.org/jira/browse/WSS-192 At this point, I think it's more worth it to figure out what else needs to be done on trunk and just get 1.6 released. I'd like to move CXF 2.3 to 1.6 if possible. I'd also be quite OK with pushing the SAML2 stuff into just 1.6 and getting it out. Thoughts? Dan > > Colm. > > -----Original Message----- > From: Daniel Kulp [mailto:[email protected]] > Sent: 28 April 2010 14:31 > To: [email protected] > Subject: wss4j performance results..... > > > I'm not sure how many of you have seen this yet, but I wanted to point > this out to you: > > http://www.ibm.com/developerworks/webservices/library/j-jws14/index.html?ca > =drs- > > Basically, as part of Metro 2.0, Sun completely redid the XWSS library > to support better streaming while processing. All that work pretty much > just brought it up to about the same level as WSS4J. I just want > to say nice job to all the folks involved with WSS4J. It's standing the > test of time. :-) > > I'm not exactly sure why they can sign things faster, but WSS4J is faster > for a sign/encrypt scenario. Something to look into. :-) -- Daniel Kulp [email protected] http://dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
