Hi Michael,

On August 15th, 2005 you wrote:


Where is Prince at now with regards to event handling and timeout control in .NET and VB/VFP?

-John

John Clarke
Cornerstone Systems Northwest Inc.

The COM interface has an event called "Message" that is raised for each error/warning message emitted by Prince, while the .NET interface currently does not have any events.

Neither interface has timeout control; are you looking for a way to kill it if it takes too long?

Ultimately, I want to be able to gracefully kill a Prince instance if the process is taking too long or too much memory. Icing on the cake would be to have onPage-type events for progress reports and estimated time to completion etc. (not just error messages).

Currently, I'm handling timeout through an OS shell and the command line but this doesn't take advantage of the COM or .NET interface features.

Another way to approach the primary timeout issue would be to add 2 new command line switches/properties:a) timeout in seconds and b) maxmemory in bytes (or something).

-John

John Clarke
Cornerstone Systems Northwest Inc.