Re: Long-running webservice, options? -- WEB400

Subject: Re: Long-running webservice, options?
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Mon, 15 May 2017 11:18:59 -0600
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Jon,
That sounds like what they had in mind.

If I understand correctly, the Windows team is comfortable with exposing a
web service themselves, that your program could invoke when their previous
request to your web service has completed. That would be consistent with
the .Net shops that we've dealt with.

Your CGI program could return a quick response after submitting a job to
handle their request, which would run asynchronously.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.