I guess the real question that I have is why the move? Was there something missing from webware that you found in skunkware? I'm sure there are hundreds of good reasons to use one framework over another, included personal preference, I only ask so that we can make webware better.
Other wise, I would love to keep an eye on this thread, I've often thought of moving sites from one framework to another, but usually when you get into it, unless your really motivated its generally a pain in the backside Jose > -------- Original Message -------- > Subject: [Webware-discuss] Some notes on porting from Webware to > Skunkweb > From: [EMAIL PROTECTED] > Date: Sat, March 05, 2005 1:01 pm > To: [EMAIL PROTECTED], > [email protected] > > I have nearly completed a test port of my hobby curve and > surface fitting web site, http://zunzun.com, from Webware > to Skunkweb. The conversion is sufficiently complete for > considerable comparitive testing to be made. I would like > to make these notes available for both mailing lists, if > anyone is interested in this subject. > > > First, here is the current Webware-generated home page URL: > > http://zunzun.com/Fitter/HomePage > > and the equivalent Skunkweb-generated home page URL: > > http://zunzun.com/sw/test/PageFiles/HomePage.py > > > You'll see that the Webware page uses a URL-based session > ID when it loads, and this is not yet implemented in Skunkweb > so those sessions are limited to being cookie-based. This > is a limitation for a single user of the web site who is too > paranoid to turn cookies on. The thousands of other users > have no problem with cookies, and although I would rather > have a solution that works for everyone a 99.95% success > rate here is good enough for me. I will need to add a cookie > test to the home page, I guess. > > > Conversion was fairly straightforward, no changes to the > Webware Page class hierarchy subclassing or existing object > model were needed. The main changes were: > > 1) Accessing request and response data. These changes were > trivially on the order of cut-n-paste across files. > > 2) Removing thread-specific data storage, as it is not > needed with Skunkweb. > > 3) Moving some minimal amounts of thread-shared site constants > around a bit. > > 4) Removing thread locking/unlocking around non-threadsafe > third-party libraries as this is not needed with Skunkweb. > > 5) Calling the Python pages directly, as in the Skunkweb > URL above. I'm porting and not yet converting, for example > I have not used Skunkweb's caching or STML. > > > James Phillips > http://zunzun.com > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Webware-discuss mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/webware-discuss ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Webware-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/webware-discuss
