How do I do that? (I feel stupid now...)

BTW, I should mention that I'm using SecureConversation as well.

Thanks for your help!

James Hancock

hi James,
this may not be the answer your looking for but it is quite a fundamental
problem you face so some lateral thinking may be in order.

how about you make the users aware of the fact that they may have to wait up
to 10 minutes if they haven't logged in for a long time.  here is what i
might do:

run the web method synchronously as normal, but the server starts the
processing on a new thread and returns a GUID corresponding to the job ID
for the client.   you could maintain the list of current jobs in a static
hashtable on the server (or thread pool or backgroundworker objects etc) and
remove them from the list when they are complete.  you could also store
error / status information in the hashtable.  the server might even be able
to estimate how long the job will take based on whatever is in the database,
and then you could return this information with the initial web method call
to the client.

your client invokes the web method, get the job ID back straight away, and
then polls the server at intervals with the job ID until it is complete.
it sounds like the timeout problem is on the client side rather than the
server side so this approach should overcome that.  i hope this suggestion
helps.

tim mackey.