On Tuesday 16 December 2003 10:05 pm, you wrote: > Hi, > > I have now AS 4.0 on my production server, and it is working like a charm. > > I would to thank the AS core team ;-) > > I also installed TTrace, and the package looks really great, but I needed > to make some minor changes to my code : > > * all ns_register_filter and ns_register_proc procedures need to have only > 1 arg. > > * I have an old page (dbtest.tcl) from ARS digita that is checked by my > keepalive server to see if the web server is ok. > > In this page I have code like that : > > ns_return $conn 500 text/plain "failed" > > It's not working with the TTrace package, I had to change with : > > ns_return 500 text/plain "failed" > > and it's fine. (looks like the $conn var is not set anymore with TTrace) > > It could be cool to add that stuff into a "migration" part of the TTrace > README for other users. > (I can try to send you a .txt file with my experience if it can help). >
Thanks for sharing your experience. I must add to this, that the "ns_conn $conn" is the pre-3.x construct which is being carried with AS over and over for the backward-compatibility. I will have a look into this (as promised) and try to find a solution which won't require any code changes in order to utilize the ttrace package. It is just the fact that we do not have any pre-3.0 code arround, so I never cared about the (those) compatibility issues. What I'd be interested to see is the effect of using the ttrace... Were there any noticeable performance degradations (should'nt be), what is the average memory footprint of the app with/wihout the ttrace enabled, what is your thread creation time with/without the ttrace enabled ? Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
