Damon Courtney schrieb:
It's sad, but it won't be the first project to fall by the
wayside. Especially not in the Tcl world. Personally, I'd like to
see a final 1.0 release put out. Maybe someday, someone will come
along and pick it up. In the meantime, it doesn't mean you can't or
shouldn't continue using it for production / development code. It's
perfectly capable in its current form, and it's easily extended with
Tcl extensions.
How much more do you really need from Rivet itself? It's just a
bridge between Apache and Tcl. It just doesn't bridge between Apache
2.x and Tcl. I guess that's the big lacking feature.
Having started the port of Rivet 2.0, I have to admit that I don't have
the time for it as well anymore.
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.
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? The
advantage would be to have a low level layer in between Rivet and
apache. This makes abstraction easier and if something changes in
Apache, the only work would be to adapt it in mod_tcl. Rivet would not
be affected. Also, the big picture could be that it is possible to run
Rivet on top of tclhttpd or AOLServer.....
Just some thoughts for someone who likes to dig into this - I would, but
I can not guarantee that (resp. when) I'll have the time for it.
Eckhard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
