It appears that with the MakeAppWorkDir utility, the idea is to support users creating their own working directory.
However, Launch.py tries to load ThreadedAppServer out of WebKit, and not out of the users specified directory making it difficult for a user to create their own AppServer. Furthermore, ThreadedAppServer is not easily subclassed, without defining your own main and run functions. Is there any interest or reason to extend ThreadedAppServer.main and run such that something which implements an AppServer interface can be passed in as an argument? A current option which is to WebKit.ThreadedAppServer, and then re-defining WebKit.ThreadedAppServer.ThreadedAppServer to be your own AppServer. However I don't really think this subtle style of redefinition is really a good idea at this level of a project, because it can be very obscure especially to a new python programmer what is going on. So is this capability something others want? Is it a reasonable goal that most behaviors should be changeable by subclassing, and that the typical developer should not have to make changes in the WebKit directory short of bug-fixes. Should the Launch.py and ThreadedAppServer.py be upgraded to support passing in an AppServer interface? -- Stuart Donaldson ------------------------------------------------------- This sf.net email is sponsored by: Are you worried about your web server security? Click here for a FREE Thawte Apache SSL Guide and answer your Apache SSL security needs: http://www.gothawte.com/rd523.html _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
