The timing info is curious because libxml does the job with very little cpu time, it is the real-time delay that is the problem.On identifying the location of the delay (since it is wall-clock time we are talking about), it should be sufficient to do splits between each method call (could just be t1=Time.now, etc) to identify where the delay is.
Or just run it in ruby-prof and you'll see what each method is doing... Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ libxml-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/libxml-devel
