On Wed, 2002-11-13 at 17:43, Stuart Donaldson wrote: > I was looking for a clean way to implement my own Session class. > > It appears that this is passed into the constructor for Application() > however the specific Application is called for out of AppServer which is sub > classed by ThreadedAppServer. > > So, my plan was to create: > > class MyAppServer(ThreadedAppServer): > ... > def createApplication(self): > return Application(server=self, sessionClass=MySessionClass) > > It seems like the lower layers are pretty well designed with the idea of > supporting this kind of behavioral change through sub classing. It's just > that the ThreadedAppServer module didn't carry all of that through, and > seems to be designed a little more as a terminal class.
That was a portion of the design that was never really fleshed out. Another approach is MiscUtils.MixIn, which might work better for you, since it doesn't require subclassing, which makes it easier to upgrade and easier to exchange and intermix code. Ian ------------------------------------------------------- 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
