On Jan 27, 2011, at 9:12 AM, Clif Flynt wrote: > It seems to me that there's more web activity now than there's > been in several years. This might just be because I've got a contract > doing some web-work for a change, but... > > In the Tcl arena, we've got: > > tclhttpd - old, reliable, stable and obsolete (but I use it). > wub - new, snazzy, up-to-date and fluid (I use this one, too). > rivet - stable, integrated with the most-used server (yeah, I use this one). > ?others? - I probably missed a dozen or two that I don't use. > > Would it be reasonable to do a compare-and-contrast panel at the Tcl > conference? Would anyone be willing to step up and defend their turf?
I'm hoping to go this year and drag Karl along. He's quite a busy guy though, so I don't know if he can leave his commercial endeavors for 3 days and do something academic. 0-] If I can make it this year, I'd be happy to sit in on a panel as Rivet rep. > I use tclhttpd when I've got a fairly simple task that doesn't > need anything fancy. I used tclhttpd to set up sample exams for my students > when I taught Tcl at EMU - a separate tclhttpd (and port) for each exam, > was trivial. > > I use wub for the Tcl Community Association pages mostly because > the pages are co-hosted with the wiki.tcl.tk, and that's wub. It's nice > in that it supports lots of new stuff. Less nice because it changes > and grows. > > I'm using rivet for a commercial task because Apache is solid and > nobody questions using it. Rivet isn't moribund like Tclhttpd, but > it's not so fluid that I worry about my code breaking with the next > release. I use tclhttpd in the same way. Particularly when I'm going to create a simple, embedded application or something. I can run it anywhere I can run Tcl with no installation or fuss, and that's a huge plus. I've never used Wub just because I already had tclhttpd and Apache / Rivet. I didn't really feel the need to throw in another technology when my needs were served by two others. I use Rivet for the big projects. I like having Apache there where it really counts. I know it will get the job done and that despite problems with my Tcl or maybe even problems in Rivet, Apache will run like a champ under tremendous load and never let me down. As for Rivet itself, the nice thing about it is that it's pretty small when you look at it. Rivet is really just doing some parsing and then eval'ing of objects within an interpreter in the Apache process. With every major upgrade of Tcl I've been able to just compile Rivet and go. So Rivet has grown with Tcl. This last project I started, I compiled the 8.6 HEAD with TclOO and TDBC and plugged it in, and I was using TDBC to talk to MySQL in minutes. With all the work Massimo has done on the builds, Rivet compiles with ease now. The same could not be said of previous versions. And, because it's built on top of Tcl, you have powerful packages available for just about everything you need. Whenever I compile PHP, I always have to figure out which of the 1000 --enable-X options to enable to get the support I need built into the module. D --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
