At 12:53 AM 5/30/01 -0500, Ian Bicking wrote:
>On the HTTPServer thread... wouldn't it be easiest to make a
>HTTPServerAdapter? Or would this imply a speed hit for the socket
>connection that was the point of using the embedded HTTP server in the
>first place?
Yes, there already is an HTTPServerAdapter -- it's called Apache +
mod_webkit :-)
I think of HTTPServer as something you would use if you wanted to embed an
HTTP server into another application to provide a web-based interface to
that application without needing a separate web server. In some
circumstances this can be very useful. It's also convenient to use for
development since it's so easy to get started with it. For actual
deployment, I assume most people would go with Apache or another web server
to get the benefit of SSL and/or to be able to serve static files directly
from the filesystem.
>Also, eventually there *is* going to be a FTPServerAdapter... if
>someone else doesn't write it, I'm sure I will. With more than one
>server involved it's easiest if the AppServer is always expected to be
>in place.
I didn't quite get this. Are you proposing writing an FTP adapter in
Python that would accept FTP requests and forward them to the app server as
though they were HTTP GET requests?
I think rather than write more and more adapters I prefer to go with Chuck
and Tavis's goal of allowing the app server to listen on different ports
and different protocols.
--
- Geoff Talvola
[EMAIL PROTECTED]
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
