Re: [Webware-discuss] an informal WEP: refactoring webware's package layout and component system

[Geoff T. <gta...@na...>]

At 03:06 PM 11/1/01 -0800, Chuck Esterbrook wrote:
>At 02:06 PM 11/1/2001 -0800, Tavis Rudd wrote:
>>    * some of the kits should really be part of WebKit's core.  For
>>       example, COMKit functionality can easily be coded directly into
>>       the AppServer (or MultiPortServer in the redesign code I've
>>       been working on).  It took 8 lines in the redesign code, rather
>>       than 93 lines in 2 extra files and 4 directories with COMKit.
>>       Ditto for TaskKit.  The code for managing SessionStores in the
>>       redesign code was more compact, more efficient and much simpler
>>       without TaskKit.
>
>I don't have a strong opinion on COMKit either way. Maybe Geoff, who wrote 
>it, does.

Because COMKit is so simple, it might be better to roll it into the 
core.  Also, COMKit is useless outside of WebKit, so there's no strong 
argument for keeping it separate.

>I strongly disagree about rolling TaskKit into WebKit. How would someone 
>use TaskKit independently of WebKit, if it were rolled into WebKit? I 
>think the answer is that they couldn't. Ditto for MiddleKit and UserKit.

We use TaskKit in non-WebKit applications.  It's useful in its own 
right.  Let's keep it separate.


--

- Geoff Talvola
   gtalvola@NameConnector.com