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:
and the equivalent Skunkweb-generated home page URL:
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.
Get latest updates about Open Source Projects, Conferences and News.