At 01:00 PM 6/14/2001 -0500, Ian Bicking wrote:
>Glyph Lefkowitz <[EMAIL PROTECTED]> wrote:
> > Where should I begin in making my webserver more webware-friendly, and in
> > making webware more twisted-friendly?
>
>After reading a little about Twisted, it looks like it overlaps with
>Webware in AppServer -- or, rather, Twisted is what the AppServer
>would be if the AppServer were everything people wanted it to be.
>
>However, I don't think the interface between AppServer and the rest of
>the system is very well defined -- no one's really expected it to be
>replaced with non-core components. Another layer of abstraction --
>the adapters -- is the way replaceable components have been created.
>But these really only cover HTTP. Perhaps the notion could be
>extended to other protocols, but Chuck and others think it's better to
>extend AppServer to support the protocols itself.
I didn't understand the above paragraph and that might be indicative of a
miscommunication.
My intent is that AppServer have a list of ports each of which has a
protocol. Each protocol handler itself would be a subclass of something
called Protocol or Connector.
So if you want to add protocol FooBar, you don't make a subclass of
AppServer, you make "class FooBar(Protocol): ..."
Also, you mentioned "the adapters -- is the way replaceable components have
been created". Say what? Adapters get web servers and the app server to
talk. Period. They are not about extending the app server's functionality;
only its range of web server integration techniques. Hence adapters are
appropriately centered around HTTP.
Whether or not you would need adapters for other protocols is purely a
function of whether or not you will connect directly to the app server.
e.g., if you support FTP and your clients hit the app server directly,
there is no need for an adapter.
Note that when I say "adapter", I mean so in the "WebKit/Adapter.py" sense
of the word as well as how it is used in the Install Guide for WebKit.
Obviously, adapter is a fairly generic term and could be used multiple ways.
>Webware *wants* to support more than HTTP. I personally would really
>like FTP. By hooking the non-HTTP part of Twisted into Webware, you
>would be providing something we don't already have.
Does someone want to do the work on AppServer.py to make it support
multiple ports and protocols?
The key to a successful contrib would be focusing on this one item, as
opposed to rewriting WebKit or creating a contrib that has 8 unrelated
features. Also following the Style Guidelines.
-Chuck
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss
