From: Alexander Peshkov (email@example.com)
Date: Fri May 21 2004 - 02:32:46 PDT
As Nikolai has admitted in his recent post: http://xep.xattic.com/lists/xep-support/2045.html
performance of XEP.Net is lower than of its Java counterpart, because
of .Net version is a port of Java one it's efficiency is lower.
As for the problems with COM wrapper - judging on the symptoms you
describe it's a typical memory leak. We believe that our COM
wrapper does not have such leaks itself (it was thoroughly tested in
this respect) thus I suppose that the source of the problem may be in
your code or it maybe a case of .Net-COM inter-operability issue. It
definitely looks like XEP COM wrapper instances are not released by .Net.
Alexander Peshkov mailto:firstname.lastname@example.org
KN> Hi ,
KN> Generating PDF with the .Net library takes a long time compared to the Java version.
KN> If we use the COM library provided by XEP it is faster than the .Net version. But on a server it gets slower and slower and fails after a while saying cannot set stylesheet.
KN> Any alternate or workaround to this problem.
KN> Thanks in advance
KN> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
KN> in the body of the message to email@example.com from the address
KN> you are subscribed from.
KN> (*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to firstname.lastname@example.org from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Fri May 21 2004 - 02:46:49 PDT