Why do we need a MetaKit db driver? I expect it will be possible to run AOLserver out of a Starpack without calling a metakit db from inside AOLserver.
Jeff Hobbs wrote: > > If AOLserver could make use of the VFS capabilities of Tcl > > 8.4 then it could be included in a Starpack. If we could > > VFS capabilities are one thing, which AOLServer should support > (part of the core). To be included in a starkit or starpack > (see http://wiki.tcl.tk/starkit) requires a thread-safe metakit, > and I'm not 100% confident that it is after talking with > Jean-Claude Wippler (author of metakit). That would be the one > thing that needs verification. The AOLserver would clearly need the VFS for adp and tcl files. But if the database application were something like BerkeleyDB, which is thread safe and 2-phase-commit etc., then why use MetaKit as the *application* database? The model would be AOLserver linked with C/C++ app code with Tcl and adp and a BerkeleyDB database with driver. Then wrap all of that up in the Starpack. AOLserver does not need to call MetaKit directly, it would only need to be able to run inside the VFS. (Or course, it also needs to run on Windows.) Of course, given that the target for this possible app is a single user version of a multi-user AOLserver web site, it might be possible to live with MetaKit with single threaded access. > > I do know that people have turned tclhttpd into a starpack, so > such a thing is possible. Also, any extensions used have to > either be statically built into the base kit or be stubs-based, > as that is a starpack requirement (can't have dependencies on > external Tcl/Tk libs). I would rather package the current AOLserver app without needing to rewrite it in tclhttpd. > > > Additionally, [incr Tcl] doesn't work inside AOLserver right > > now. Does anybody know why? Does anybody know whether it > > could be made to run correctly inside AOLserver? > > I don't know why, but xotcl does: > http://www.xotcl.org/ > If you don't already have a body of incr Tcl code, just use > xotcl (more "Tao of Tcl" compatible in any case). True. But XOTcl is a higher learning curve than Itcl given that I know Itcl and our developers are used to C++/Java class models. Also there are good books on Itcl but not much tutorial and training material for XOTcl. I think it would be a win for AOLserver if both Itcl and XOTcl would work. > > Jeff Hobbs The Tcl Guy > Senior Developer http://www.ActiveState.com/ Greg Wolff [EMAIL PROTECTED] -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
