Re: Apache directive syntax

[Rob Dixon <robertsdixon@xxxxxxxxx>]

Many thanks
<snip>
You say the initial program must only be called once. I'm not sure if that
is possible. I guess it would work as long as the initial program doesn't
start the persistence and is just there to give you a link to the second
program
</snip>
 That is exactly how it works. The initial program has no output - it
simply calls the CGI program (indirectly) and that deals with persistence.
As I have said, it all works fine with the original HTTP server.

Persistent CGI isn't complex once you understand it, but I just don't
understand how to configure Apache to replicate the original HTTP server.




On Tue, 11 Dec 2018 at 14:06, Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx>
wrote:

> <snip>
> The other difference is that I have to distinguish between the initial
> program which calls my CGI program (indirectly) and that CGI program, as,
> rather obviously, the initial program must only be called once.
> </snip>
>
> You say the initial program must only be called once. I'm not sure if that
> is possible. I guess it would work as long as the initial program doesn't
> start the persistence and is just there to give you a link to the second
> program. Here is how persistent CGI works with Apache on the IBM I to the
> best of my recollection.
>
> Open program /cgibin/mycgi.pgm
> The very first output must be Accept-HT:myhandle
> Myhandle has to be unique. It is what tells apache to leave this program
> open, and how to get back to this instance of the program.
> You output the rest of the page as normal. In there is a link that posts
> to /cgibin/mycgi.pgm/myhandle/
> When you submit that post, the same instance of mycgi.pgm is called. If
> you need multiple programs, you would need to call them from the first
> program.
>
> I have had it working before as a proof of concept, but like you, I was
> extremely frustrated with how complex it was to make it work. In the end it
> was decided that rewriting everything in PHP and using stored procedures
> was easier than trying to tack persistent cgi over our existing screens and
> workflow.
>
>
> [https://www.medtronsoftware.com/img/MedtronMinilogo.bmp]  Kevin  Bucknum
>                    Senior Programmer Analyst
>                    MEDDATA / MEDTRON
>                    120 Innwood Drive
>                    Covington LA 70433
>                    Local: 985-893-2550
>                    Toll Free: 877-893-2550
>                  https://www.medtronsoftware.com
>
>
>
> CONFIDENTIALITY NOTICE
>
> This document and any accompanying this email transmission contain
> confidential information, belonging to the sender that is legally
> privileged.  This information is intended only for the use of the
> individual or entity named above.  The authorized recipient of this
> information is prohibited from disclosing this information to any other
> party and is required to destroy the information after its stated need has
> been fulfilled.  If you are not the intended recipient, or the employee of
> agent responsible to deliver it to the intended recipient, you are hereby
> notified that any disclosure, copying, distribution or action taken in
> reliance on the contents of these documents is STRICTLY PROHIBITED.  If you
> have received this email in error, please notify the sender immediately to
> arrange for return or destruction of these documents.
> --
> 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: https://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/web400.