On 02/24/2003 08:19:19 AM Clark wrote: >Really; I think either choice is probably very good. I'd say >webware is probably a bit more mature, and if you already have >Apache and don't really need "chat" and "ftp" and other services >besides "http", then I'd pick Webware. On the other hand, if you >are writing a peer-to-peer thingy, I'd pick Twisted. > >As for portability between them... Most of my webware code >(inherits from Page) moved over quite nicely with little pain. >The issues when switching frameworks: (a) sessions, (b) database >connections, (c) threading issues for shared memory/resources, >(d) minor field name changes. Overall, you could probably port >a medium sized project between them in a long weekend.... so, >really, pick either. If you don't like one, switching wouldn't >be all that painful if you changed your mind later.
Thanks for the summary--it's hard to understand Twisted with the docs out there now, so comments like these are useful--particularly since the Twisted docs don't seem to paint a bigger picture of it. That it has been evolving from some kind of multi-player game(?) framework does not help! ...Edmund. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
