But the user process needs Active4D too.
Like this.
normal process:
-analyze if it is a user-request
-give a message to the user-process with the streamref.
-then choose if Active4D should handle the request, or if it is a standard
request.
I understand. You need a hook before Active4D is called.
Would it be possible for the first set of parameters like host, url etc. to
always be at the same position, so that we can use them with a constant
iterator, so that access to these values can be handled quickly?
That isn't necessary. You will have a collection handle. To get the host you will use:
$host := get collection($ioRequestInfo; "*host") $url := get collection($ioRequestInfo; "*url")
Is that quick enough?
What is with the performance? Until now, I tried to make my system veryYes, the pre-execute hook will be given handles to all of the request collections, with which you can use any of the generic collection commands.
fast,
so that all the requests like pictures, scripts, css and small not dynamic
html-pages are answered very quick.
First of all the hooks will not be called unless you set a flag in Active4D.ini. The performance hit of calling these hooks is tiny.
And will it be possible to work with active4D as it worked before?
Of course. You are still free to change the shell however you want. I am just adding some features that will hopefully make it easier for some people to make modifications to the standard behavior without modifying the shell.
Regards,
Aparajita Victory-Heart Productions [EMAIL PROTECTED] www.aparajitaworld.com
