What is the thinking behind not (re)using the same jobs/threads?

[https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: 02 February 2017 23:08
To: WEB400 (web400@xxxxxxxxxxxx) <web400@xxxxxxxxxxxx>
Subject: [WEB400] Segment webservices

I'm getting into webservices. I'm using an Apache instance with RPG CGI programs that call service programs. Everything seems fine now, but... Right now all the services run in the same job(s). I have a handful of services now, and I'm starting to think I want to separate them so they don't all share the same job(s). I know I could just create additional Apache instances, but that seems like overkill. Is there a better way to do this?


I'm not dead-set on RPG CGI, but I am limited to software we already own.


TIA
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.




________________________________
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.