give more details... anyway, you can always have the server updates its status in some variable and have the client poll the server about its status periodicallyor if you are using remoting, look into Asynchronous Remoting http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconasynchronousremoting.asp
to saucer: thaks!1 "periodically" means using timer control? 2 I use web service detail: JBoss web service have methods : string getTask() and object getResult(string theresultofgettask). the gettask method is quickly, but the the result of gettask method maybe not really prepared. when call getResult(...), there is an exception(null exception). There are also a method of string[] getFinishedTask(), whose result is the prepared result of gettask method. So the question: Should i always all the getFinishedTask to confirm and to call the getResult method?
>>1 "periodically" means using timer control?what is your client? .NET client? yessince you don't have something like getStatus() or isDone(), then that seems the only way to go
anyway, you can always have the server updates its status in some variable and have the client poll the server about its status periodicallyor if you are using remoting, look into Asynchronous Remoting
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconasynchronousremoting.asp
thaks!1 "periodically" means using timer control?
2 I use web service
detail:
JBoss web service have methods : string getTask() and object getResult(string theresultofgettask). the gettask method is quickly, but the the result of gettask method maybe not really prepared. when call getResult(...), there is an exception(null exception). There are also a method of string[] getFinishedTask(), whose result is the prepared result of gettask method. So the question: Should i always all the getFinishedTask to confirm and to call the getResult method?