On Jun 1, 2005, at 8:18 AM, Warren Young wrote:
Glen Mazza wrote:So I don't think FOP would ever know itself how much finished it is with its input, and hence would not be able to report on it.In that case, the program driving fop could set up a named pipe, and provide the fo file through that. Then the driver program would know where fop is reading in the file, and can infer progress from that.The only problem with this approach is that it's hard to do portably. But if you're on some *ix type system, it's pretty easy to do.
FOP uses a logger object to report information, warnings, and errors. For embedded FOP, I would write and install a custom logger object to echo the current page number into a progress box.
For servlets, cache and send back the growing log report then use a META tag to have the browser refresh one second later. Use servlet sessions to connect the right FOP thread with the right browser.
Been doing it for years this way. --will gilbert
smime.p7s
Description: S/MIME cryptographic signature
