Best practice for kicking off and monitoring a long-running process over RPC

2009-10-30 Thread pjaromin
I'm writing a remote service that executes a long-running process that I'm updating on the client-side using a progress bar widget. What I'd like to do is have two methods in the service: String longRunningProcess(Request request); Progress checkProgress(String id); The question is, what's

Re: Best practice for kicking off and monitoring a long-running process over RPC

2009-10-30 Thread David Durham
On Thu, Oct 29, 2009 at 4:41 PM, pjaromin patrick.jaro...@gmail.com wrote: I'm writing a remote service that executes a long-running process that I'm updating on the client-side using a progress bar widget. What I'd like to do is have two methods in the service: String

Re: Best practice for kicking off and monitoring a long-running process over RPC

2009-10-30 Thread david.durham.jr
On Oct 30, 12:56 pm, David Durham david.durham...@gmail.com wrote: too.  I'd probably use a database for the uuid gen (could just be a sequence) and to start the state of processes machinename/running/finished.   meant *store* the state of the processes

Re: Best practice for kicking off and monitoring a long-running process over RPC

2009-10-30 Thread David Durham
On Fri, Oct 30, 2009 at 12:56 PM, David Durham david.durham...@gmail.com wrote: You can get info from the process via output stream and error stream. Uh... the input stream and the error stream provide info from the process .. not really selling my consulting skills here .. -Dave