But lately I thought about it, especially the restructuring issue. And I
thought it could be considered to put a new version of Rivet on top of
mod_tcl. Mod_tcl does bridge between Apache and Tcl, and it works for
Apache 2 as well. It also works on windows - some time ago I spent an
afternoon to port and compile it with Visual studio for Apache 2.2.
Maintaining mod_tcl and adapting it for new Apache versions is easy,
just because mod_tcl is very small and easy in terms of functionality.
It's basically a low level binding for the Apache API - not less and not
more.

A long time ago, that was sort of my idea for the future of the
Apache/Tcl world...

So what Rivet essentially does is parsing the Tcl code in .rvt files and
I wonder if this could be implemented in pure Tcl on top of mod_tcl?

Mostly.

be affected. Also, the big picture could be that it is possible to run
Rivet on top of tclhttpd or AOLServer.....

That's one thing I think I have some personal responsibily for
screwing up.  We should have done more in the Tcl/Web world to
integrate all these different things into at least a basic platform,
because having such a wide variety of different things is just
confusing and disconcerting for people.

In any case, yeah, I'm basically not interested in doing much work
with Rivet beyond an advisory role.  Rails has been far, far more
productive for me because there is so much out there that I can just
take and use, without having to build and maintain it myself.

--
David N. Welton
- http://www.dedasys.com/davidw/

Linux, Open Source Consulting
- http://www.dedasys.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to