HTTP API and multiple connections -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: HTTP API and multiple connections
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Date: Mon, 21 Jan 2019 23:08:21 -0700
Arc-authentication-results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=VOZUs4o+; spf=pass (google.com: domain of charles.wilt@xxxxxxxxx designates 209.85.220.41 as permitted sender) smtp.mailfrom=charles.wilt@xxxxxxxxx; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=to:subject:message-id:date:from:mime-version:dkim-signature; bh=rMET4laupRRKhoiwLVnhtH4j0VqI+u8MDPkO2gEF7mQ=; b=0vzu3MQkLBu6TcP115jIBA5i22sdkneKz8M9xPtFKKhASqetTy8S/668wjyQuTHvU2 JmIDnIvdtIUyOIyUZHgi6X3g/2cHQuEdBhay35DTPA1sr0X0wtQNAzdwV4a5ubMYxkk9 KdR1YMkbmMMWhg/+cNcVMGyJUzIXV+9lDJcFHt7j05ZR6VuJKmyHB+YUg1hrRstYB5eW uoJJxKhdA7fHvc76PEVxo72aSA1yssgCpzpweRyG0UT4mr/DgaVy71c7qE7Bc28Ergyp B7N2cKslQbeWa/xWoPgEm6CdQCUXMSOQkyOfHAnm9cGPgH/3bHE62z06hRHQyvdT4OPq Ia/A==
Arc-seal: i=1; a=rsa-sha256; t=1548137312; cv=none; d=google.com; s=arc-20160816; b=pdqEfnyLzoV/sx/xz1xdXthWfqxY5ywSBV3Vn2vyW6iYLmyrrZxfQc+ojz3ekaNeRM +q1cW1FoEuprxJ6P/PkGnM/fXguEchljcz/M6HstCeEg4islI18Yd3AhUzgRoIs5yTWM mZMw8ncU0pm6HdjMEdjPK8oyIH12mWQcX8D0uDhlcvrdvkDBzqbJ868HiTmad3UoQp4U znPBpHfDTSapwZWatTUSxBxf43ofHxHzChbxh0vLL+wkeVTpPPuyV90Kqm6GHjYWAQJG ikZ+pIXYKNecQfcc59AiFJstbOW1VhGYhuLPzDKF3C31+Aaajb0pB37e3H3gOOQuggDh nsqQ==
List-archive: <https://archive.midrange.com/web400/>
List-help: <mailto:web400-request@lists.midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.lists.midrange.com>
List-post: <mailto:web400@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@lists.midrange.com?subject=unsubscribe>

Given
- PGMA using HTTP API to contact ServiceA
- ProcB in a service program which calls ServiceB

If PGMA has an open to connection to ServiceA, but between request calls
ProcB, is that asking for trouble?

I saw an issue with http_xproc(HTTP_POINT_ADDL_HEADER), since both PGMA and
ProcB were setting it, I had to reset it in PGMA after my call to ProcB.

Is there anything else I should be concerned about? At first glance, we're
not using any of the other http exit points. I can see where debug
settings might be an issue.

Thank you!
Charles

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: HTTP API and multiple connections , Scott Klement

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.