Is there a way to set the Timeout on RemoteProcedureCalls?
I am doing some fairly lengthly processes on the server, and I am getting TimeoutErrors.
Another though I had on this is what if I started another thread on the server in the RPC to do the work so that the RPC could return right away? I don't need to return any data, as it's just doing work with the data. Then I would never get a timeout error. However, if there were some other error, I don't know how this would get back to the client unless I created an ErrorLog table on the server and queried that for errors.
Edited by gregweb - 03-Feb-2011 at 9:09pm