And/or, we could distribute all of the useful "kits" under the Webware umbrella "brand" and do releases of each. If we use distutils eventually, this will be transparently easy for users to use and install.
As I mentioned, my proposal would be to fix/remove dependencies as necessary. Clearly, if Task-kit is so fundamental to webkit that it cannot be fixed/removed, then there's an exception to my idea. But I doubt that sweeping through a dictionary of session id's and operating upon them needs a whole "kit".
deelan wrote:
Tracy Ruggles wrote:
I would consider the TaskKit as "core" to the project, at least for what we do with it, but also I think it's used
by the session sweeper isn't it?
i use it a lot too, i periodically generate XML feeds for a couple of webware-powered blogs and i find very useful to have some some of task scheduling inside webware.
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
