Michael Link <[EMAIL PROTECTED]> writes:
> Cool, I've subscribed. Do you have any set of goals listed, or just
> a general idea of where you would want the project to go? I know my
> personal goal was to create something like mod_perl but with TCL
> (and a hell of a lot cleaner/lightweight). Otherwise ask any
> questions you wish :) Thanks.
Well, a few initial observations about what I'd like to do, and a few
about the code you have already:
I would like mod_tcl to be something very 'neutral' (i.e., nothing
like dtcl or neowebscript built in), and very flexible, so that
something like dtcl can be built on top of it. I also hope that it
would be possible to keep things relatively speedy - people won't
accept dtcl or nws built on top of it if this slows them down.
As far as your code, there are a few things I noticed:
It's C++ - personally, I would rather just use plain C because it's
smaller, faster and probably better implemented across a variety of
platforms.
It needs to seperate out the 'utility' stuff (like all the mysql
calls) from the core code. There are several ways to access mysql
from Tcl - and a 'neutral' mod_tcl won't force one of them on users.
I think that libapreq also provides a good API for getting post data,
cookies, uploaded files and so forth, and would prefer to use that, so
that we share more code (the Perl guys use it as well). This is
another thing that offloads non Apache-Tcl integration into other
places.
Personally, I would also break the Tcl commands into a seperate file,
to help organize things.
--
David N. Welton
Personal: http://www.efn.org/~davidw/
Free Software: http://people.debian.org/~davidw/
Apache Tcl: http://tcl.apache.org
