On Mar 27, 2008, at 17:41, Jason Timmins wrote:
<snip />
Sure, in an ideal world, I'd throw-out 18 months of .NET and re-
write the
whole thing in Java! I'm not going to get into a .NET vs Java
discussion.
For me, for now, .NET is what I've got and what I'm happy with....
I could
just do with not loosing 1Mb of RAM every time I make a PDF.
....I know, I'll just add more RAM!! ;-)
Reading this reminds me that one of the customers I worked for once
actually received that exact response from a software vendor.
The user/developer was so good as to investigate memory issues up to
a point where he was certain that the app was retaining heaps of
memory with redundant or obsolete info. So he contacted support, and
pointed out that the tool had serious problems with releasing caches,
and they bluntly told him that he had no choice but to either reboot
his system or buy more RAM... :-)
If you're happy with .NET, all the better. The hints provided by
Jeremias and Abel earlier should prove that a 'redesign' of your app
would only require a minimal amount of effort, with possibly
significant performance benefits. It does not seem to me that you
would literally need to 'rewrite the whole thing'.
Java is most likely already available on your system in one way or
another. If not, installing it is a matter of minutes. You're stuck
with the configuration and maintenance of the servlet container that
was spoke of, of course, but that is about the only downside I can
think of. It is a proverbial piece of cake, these days. In bigger
companies, it's even likely that one exists already, and you just
need to develop the servlet.
It basically comes down to:
- moving the related code you have in your .NET context to Java
servlet-classes, adapt the syntax (minimal effort, if you know one
programming-language, you know enough to learn them all, examples
available in FOP's source distribution (*))
- configuring the servlet context, i.e. set up mappings for the URLs
to use to call your Java code (requires some browsing through the
related specs if you need advanced stuff, but for a very basic
example, look at the web.xml example that is shipped with FOP (**)
- where you currently call out to FOP (and also Saxon, while you're
at it), send an HTTP-request to one of those URLs instead, and
process the response
Really not that hard, and I think most definitely worth a shot. Since
you're in a web server context already, the transition should prove
to be quite smooth.
(*) http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/java/org/
apache/fop/servlet/
(**) http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/conf/
web.xml?revision=627324&view=markup
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
