Hello, I'm experimenting with a small proof of concept distributed system using adapter 2.5, remoting, an IIS host and a WinForm client.

What strategy might you use to manage the situation where the user is part way through updating a complex form, left it for some time then returns to finish ther update, only to find that because the connection is no longer there, it falls over when they try to persist their changes (ie. the client idle time has exceeded the IIS application timeout limit).

At the moment the only friendly option seems to be to allow the client to silently reconnect, if the connection is no longer there, but I can't see how to do this.

Is there anything in adapter that might help me or can anyone suggest anything!

Grateful for any suggestions Regards

I can't think of how adapter would help you here, as for me this should be managed at IIS/remoting level.