Re: Long-running webservice, options?

Thanks for paraphrasing my response 😊

I tend to use API, call and web service interchangeably.

Regards,

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

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

message: 3
date: Fri, 12 May 2017 14:14:10 -0400
from: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
subject: Re: [WEB400] Long-running webservice, options?

Or have them establish a web service that you can call to notify of completion.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On May 12, 2017, at 1:06 PM, Richard Schoen <Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

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