cvs commit: tcl-rivet ChangeLog
davidw 02/01/09 17:05:01 Modified:.ChangeLog Log: Revision ChangesPath 1.16 +7 -1 tcl-rivet/ChangeLog Index: ChangeLog === RCS file: /home/cvs/tcl-rivet/ChangeLog,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- ChangeLog 9 Jan 2002 21:48:22 - 1.15 +++ ChangeLog 10 Jan 2002 01:05:01 - 1.16 @@ -1,3 +1,9 @@ +2002-01-10 David N. Welton [EMAIL PROTECTED] + + * tests/template.conf.tcl: Re-add srm.conf and access.conf - if + they aren't present, it tries to grab the ones from /etc/ - not + what we want. + 2002-01-09 Damon J. Courtney [EMAIL PROTECTED] * src/tcl_commands.c Renamed to rivetCore.c @@ -17,7 +23,7 @@ * src/make.tcl Added rivetCore.c, rivetList.c and rivetInit.c to the make. - + 2002-01-08 Damon J. Courtney [EMAIL PROTECTED] * src/mod_rivet.h Added RIVET_NEW_CONF macro to create a new rivet_server_conf.
Re: TclX commands
Damon Courtney [EMAIL PROTECTED] writes: I am currently writing up a TclX compatibility library. Of course, I can't write the whole thing, nor do I want to. I'm just writing up the basic commands that I think are really important (and mostly easy to do). Why not just use TclX if you want TclX? Or is this more of a TclX-light, with the commands you find most useful? My question is this. Should I include these commands as commands of Rivet? Or, should I include these commands in a package called Tclxcompat? Currently, I have them in a package called Tclxcompat, but I think it might be cool to have them as commands of Rivet. This sounds like non-Tcl core kinds of things that could go in their own package. Sure they would be cool commands as part of Rivet, but that doesn't mean everyone wants or needs them. Once we put something in the core, I don't think it is going to be possible to take it out again, at least not without pissing people off. -- David N. Welton Consulting: http://www.dedasys.com/ Free Software: http://people.debian.org/~davidw/ Apache Tcl: http://tcl.apache.org/ Personal: http://www.efn.org/~davidw/
Re: Rivet C code
I've mentioned it about mod_dtcl and I'll mention it here. Change the config to directories (probably the path would be relative to /usr/local/apache/rivet). That's the part I like about AOLserver - when I want to move some module I just copy modules/tcl/dirname between machines and add one line in the config. I don't want nsd's clone (actually, I do, but I'll wait for mod_tcl with that :), but the idea of splitting stuff into directories is nice. How do you mean split into directories? I'm afraid my work with AOLServer is limited. It would be even more cool to be able to add multiple lines - so that it could source multiple directories. RivetServerConf InitScript sourcedir modules/zoro/news RivetServerConf InitScript sourcedir modules/zoro/forum RivetServerConf InitScript sourcedir modules/zoro/gb Wouldn't that be cool? :) I've thought about this. It would be quite nice. It's not really that difficult to do, I think. Also, out of curiousity, when appending a 200kB global script, does it affect Apache much? I had some problems with mod_dtcl and larger init scripts. I split them into packages and did package require on top of scripts. Anyway, when ab-ing static pages with larger global scripts, I was up to 2 times slower :(. Which was kind of strange to me since I supposed global script was only loaded at apache startup (tcl8.3, w/o threads) Well, theorhetically, it should slow down the start-up time of each child process by just a little, but it shouldn't slow down the overall performance of requests. But then, I'm not sure exactly what you're doing. 0-] D
