On May 3, 2002 07:51 am, Chuck Esterbrook wrote: > Every time you think of subclassing Application just to store > application wide resources, you could just as easily (or more easily) > get along with a module for this purpose and put the objects in module > level variables. > > This might also lead to further uses of that module in other settings.
I agree. Using modules, singleton or borg classes makes much better sense that subclassing Application. The only advantage of going the subclass route is that when WebKit is extended to do multi-applications (i.e. true 'contexts') it might be desirable to have 'application/context' specific data stores or interfaces rather than process-global stuff in modules. Even then it's possible to do that without subclassing Application. On a side note, how did the Application class get its name? Tavis _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
