On Fri, Jan 04, 2002 at 04:34:13PM -0500, Geoffrey Talvola wrote: | | So I assume the trouble arises because you don't want to have | to hard-code "from V1.lib import tool"
Exactly. This would be an even worse hack, no? I suppose with a recursive perl script I could have an automated way to bump the revision number. Hmmm. | If so, then your kludge is the only way I can think of to do it. Ok. I kinda like your exception stack method, this would allow me to only have one copy of my custom loader. Hmm. | Or you could just save yourself the trouble and run separate copies of the | appserver, which is what I'm doing. I actually have about a dozen | different versions of the appserver running on one machine right now | (nightly builds from source control, plus a "deployed" version). This has the advantage of letting me deploy newer versions of Webware... HMMM. However, I really can not easily stay up-to-date with Webware since I need directory based parameters (aka /context/OBJ=293/servlet) and path based sessions... However, it has the dis-advantage that I can't share database pools across versions. I've written very specialized database pool code that uses almost all of PostgreSQL's available connections. Hmmm. Thank you so much Geoff. Clark _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
