Chuck Esterbrook <[EMAIL PROTECTED]> wrote:
[...some snipping here and there...]
> 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.
Right now the way you hook things up to the AppServer is with
adapters. They all happen to deal with HTTP, which is all the
AppServer really deals with. You could generalize this by saying the
*AppServer* supports a single protocol -- the marshal-based protocal
the adapters use. You have a vision of a way to generalize this --
but *nothing* is currently generalized. The AppServer is no more
general than the adapters. The only firm layer of abstraction is
between the adapters and the AppServer.
Twisted is stylistically quite different from Webware -- particularly
the use of attributes, where Webware uses configuration files and
subclassing. It isn't AppServer, and I can only imagine there'd be
resistance to using it as a replacement.
Twisted presents the same issue for non-HTTP protocols that the
adapters deal with for HTTP protocols. It's an external gateway for
the protocol.
Perhaps Twisted could itself be a form of protocol. I don't know what
you envision for this interface.
> 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.
I'm using adapter in terms of "that thing that connects to the
AppServer over a port", which happens to be currently implemented in
WebKit/Adapter.py, as well as mod_webkit. These are the things that
seem to me to most resemble Twisted.
> >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?
Well, I think Glyph wants to work on getting Twisted and Webware to
work together. Twisted supports multiple ports and protocols -- my
initial impression is that is pretty much what it is for. I was
trying to suggest things with that in mind.
Ian
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss
