> Just wondering who is using 2.1 and how it is going so far. If I don't
> get any more problem reports by the end of next week I will release it.
I have been using 2.1 in testing since you announced the beta on Oct 21. The
only problem I had was fixing my code to compensate for the change in
functionality of automatic relations.
One thing I would like to see in this version is the script timeout being
caught by the A4D error handler so I can display a custom error page. I'm
also having trouble setting the Log Level to catch execution errors. I set
it to 7 but that doesn't seem to work.
Anyhow, 2.1 appears very stable and is up to your usual high standards. Well
Flemming Andersen AKTIV Software Corporation
[hidden email] 723 Paskin Way
Tel: 250.727.3442 Victoria, BC V8Z 6N4, Canada
Fax: 250.727.3740 http://www.aktiv.com
>> I will be adding new hooks to the shell - one after the request is
>> received, one after execution.
> This would cover our needs if this data includes the IP address of the
> client making the connection and any cookies.
All of that data is in the headers, but at the point the hook is being
called now, the headers have not yet been parsed. It would probably be
much more useful if I parsed the headers first and then called the
hook, passuing you the headers in arrays.
> Just a thought: would it be clearer to write two method names-
> A4d_ITK_GetRequestHeader ( ->Blob )
> A4d_ITK_GetRequestBody ( ->Blob )
> or just:
> A4d_ITK_GetRequest ( ->BlobHeader; ->BlobBody )
If I change the scheme as noted above, it would become like this:
ioHeaderNames: Text Array;
ioHeaderValues: Text Array;
> For comparison, WebObjects has three hooks: one on getting the
> request, one before executing the page, one after executing the page.
> But we only ever use the last one, as it still gives us the
> opportunity to return a different page anyway.
I will be adding the first and last. In effect you have the second in
the On Execute Start handler.