Honestly, as fantastic as I think Rivet is, I myself have started
doing my Tcl development in AOLServer. At least in experimentation.
Rivet is basically dead without an Apache 2.x port, and I don't see any
developers with the time to volunteer to make this happen. I certainly
lack the time.
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.
Damon
<IMHO>
Having said this, I *LOVE* Rivet, and really enjoy developing with it,
but
given David's new found love of Ruby/Rails, I believe that unless someone
else stands up to do an Apache 2.x port, and keep the development
emphasis
going, Rivet is a dead end. While this saddens me, and I won't likely
use Rivet for any more commercial development (unless things change),
it really and truly is a useful and intuitive tool for the Tcl
knowledgeable web developer.
</IMHO>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
