Hi, can you upload the patch to Source Forge? Is this patch something that makes it so AOLserver uses the traditional Tcl way of doing dlopen() and running Modulename_Init instead of us doing Ns_ModuleInit jobbage or are we talking about something else?
Thanks, Kris On Tue, 23 Apr 2002 08:45:20 +0100, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: >On Tuesday 23 April 2002 09:37, you wrote: >> >> AFAIK, what I commited takes care of all the known patches that AOLServer >> had against the Tcl core. I believe you should be able to use the >> AOLServer head with the Tcl core head without any mods to the Tcl core, or >> any funny bugs and the like. >> >> However, if there are some "design" level issues that may need improvement, >> do tell me. >> > >Not of that sort, though. The AOLserver does seed the the connection >interpreter with commands introspected from within loaded initialized >startup interpreter. It just copies (blindly) all command structures >found in the initial interp, which causes quite a few problems with >Tcl packages planting commands with associated delete callbacks. > >So the problem is not AOLserver<->Tcl integration. The problem is >how the AOLserver does handle Tcl extensions and their registered >commands. There is nothing Tcl (you) can do about it. But there is >something AOLserver (Kris/Jim/community) can do about. >I've made a patch for 3.4 which corrects above problems. I'm just >qurious to find out if/how/when can it be included in the core >server distro. > >Hey, thanks for this memory allocator implementation! >These (speed) issues have been bugging me for months. > >Zoran
