Re: Long-running webservice, options?

In my mind you're violating the premise of a web service.

You should never try to hold an HTTP exchange very long. (30-60 seconds max)

Service calls should be quick in and out conversations.

If your client needs to submit a job, submit the job and return a job id right away to the consumer.

Then give them an API to watch for completion by polling and making calls every xx seconds or minutes.

Once complete they can pick up their file or whatever other data they need.

Regards,

Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com

----------------------------------------------------------------------

message: 1
date: Fri, 12 May 2017 13:29:34 +0000
from: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
subject: [WEB400] Long-running webservice, options?

I have an internal RPG/CGI webservice that in extreme cases can take 20 minutes to process a request (19+ minutes waiting on external services). Our Windows team (the consumers) right now is just waiting for the webservice to respond, but they want me to change my service to send a notification when it completes.

I can't think of a good way to do this.