I will use the DLL ISPAI unit small web application is not a problem, but feel the ISAPI use threads share the same DLL, very unsafe, user access at the same time is much, can appear the possibility of a conflict, an idea came to him with CGI process, efficiency is lower, but safe, ISAPI with CGI conversion is very simple, in addition to the engineering of the main program different, child form is the same,
But the trouble with CGI, took the parameters is to use the get and post, a serious mistake, can't go on, don't I c + + BUILDER6 patch? !

Try
{
TStrings * get=Request - & gt; QueryFields;//Get the Get parameter
}
The catch (Exception & amp; E)
{
ERR=E.M essage.//there EAccessViolation errors
}

Try
{
TStrings * post=Request - & gt; ContentFields;//to take the post parameter
}
The catch (Exception & amp; E)
{
ERR +==E.M essage.//there EAccessViolation errors
}



The Test - & gt; HTMLFile=CurDir + "# test. HTM";
The Response - & gt; The Content=Test - & gt; The Content ();

CodePudding user response:

There are people with CGI, I think this thing is what we use 40 is

CodePudding user response:

In c + + BUILDER6 for many years, can use it with it, even the web CGI, process speed,

CodePudding user response:

The latest patches as if also is version 10.166, for a long time without cb6, classics, mostly is enough,