xmlgraphics-fop-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Theresa Jayne Forster" <ther...@inbrand.co.uk>
Subject RE: Interrupt/cancel/abort a render
Date Tue, 06 Dec 2011 09:25:42 GMT
Craig, I agree with you, that is exactly how we process stuff here, drop a
file in a folder and then the "fopengine" picks it up - processes and then
drops the output into another folder for the original process to pick up (or
time out)

Kindest regards

Theresa Forster
Senior Software Developer

-----Original Message-----
From: Craig Ringer [mailto:craig@postnewspapers.com.au] 
Sent: 06 December 2011 03:10
To: fop-users@xmlgraphics.apache.org
Cc: Alexios Giotis
Subject: Re: Interrupt/cancel/abort a render

IMO the best way to make it cancelable is to run fop out-of-process in a 
separate VM instance that you can kill using the standard OS methods.

That's what I think I'll end up doing when I need to support 
cancellation. It's a bit of a pain and has some performance cost because 
you can't re-use the fop factory for multiple runs or benefit from some 
of fop's other caching. Perhaps more importantly it means you can't run 
under a standard SecurityManager since you need to be able to spawn new 
JVM instances. OTOH, it eliminates potential memory leaks / unwanted 
threadlocals / caches.

Craig Ringer

To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org

View raw message