From: Chuck E. <ec...@mi...> - 2001-04-10 03:12:24
|
At 12:14 AM 4/10/2001 -0700, Terrel Shumway wrote: >Chuck Esterbrook wrote: > > > No the really big difference is that plug-ins are nearly undefined. A > > plug-in is just a Python package with some extra frosting. It could be > > anything you can put in a Python package. > >That frosting seems very thin. Perhaps it will get thicker over time? We will continue to provide more conveniences for plug-ins, like running pydocs, making it easy for them to advertise admin servlets the way we have been discussing example servlets, etc. But one key to components (and therefore plug-ins) is that you can use them as ordinary Python packages: from MiddleKit import Run.MySQLObjectStore The "thin frosting" is on purpose. Thicker frosting can be provided through classes, app servers, frameworks, etc. If we need "things" that have heavier semantics, that's fine. But we should create a different sort of beast. > > >That is what I am thinking too. Just don't call the adapter/connector a > > >protocol. > > > I think I can dig the "Connector" name for what I was calling "Protocol". > > Adapter remains a logical separate entity. > >So, Adapter is a client to the Connector, and adapts the connector >interface and the external process's interface to each other. If the >external entity speaks HTTP or FTP, there is no need to adapt: the >*TPConnector already supports the interface directly. Right. But some will still prefer to run Apache rather that our native HTTP server. In fact, even I do that. > > > > Shipping generated docs? Seems like a serious waste of bandwidth. > > > > > >huh? > > > > If install.py can generate docs, why provide doc packages? > >I was grumbling because I had just installed Webware on an ancient, >memory-starved SunOS box. install.py took long enough that I got bored >and started working on something else. Then I doubt the box makes a good app server. Also, I doubt there are many app servers out there with WebKit's small foot print and great features. -Chuck |