Re: [Webware-devel] built-in http server

2004-12-01 Thread Jason Hildebrand
On Wed, 2004-12-01 at 17:28 -0500, Winston Wolff wrote: > How about renaming the current HTTPPort to AdapterPort, i.e: > HTTPPort = If EnableHTTP is True, then the built-in web server listens > to this port for web requests. > AdapterPort = If EnableAdapter is True, then the applicatio

Re: [Webware-devel] built-in http server

2004-12-01 Thread Winston Wolff
How about renaming the current HTTPPort to AdapterPort, i.e: HTTPPort = If EnableHTTP is True, then the built-in web server listens to this port for web requests. AdapterPort = If EnableAdapter is True, then the application server listens on this port for requests from the mod_webkit adapter.

Re: [Webware-devel] built-in http server

2004-12-01 Thread Jason Hildebrand
On Wed, 2004-12-01 at 15:38 -0600, Ian Bicking wrote: > > I think I prefer the name 'BuiltinHTTPServerPort' over 'HTTPPort' though. > > It's annoying long, but 'HTTPPort' is very likely to confuse new webware > > uses who haven't yet grasped how a webserver and the appserver typically > > communica

Re: [Webware-devel] built-in http server

2004-12-01 Thread Ian Bicking
Jason Hildebrand wrote: Oops, I didn't notice there is already a 'HTTPPort' option. I had meant the latter -- if any value is given for HTTPPort, we start the server. On second thought, it might be more clear to use two options: 'UseBuiltinHTTPServer' (boolean) to enable the server, and 'HTTPPor

RE: [Webware-devel] built-in http server

2004-12-01 Thread Jason Hildebrand
On Wed, 2004-12-01 at 16:29 -0500, Geoffrey Talvola wrote: > I think the situation right now is, you have to specify "http" on the > command-line in order to get HTTP at all. The port used defaults to 8087, > which can be overridden by specifying HTTPPort in the config file. I think > Jason is pr

Re: [Webware-devel] built-in http server

2004-12-01 Thread Jason Hildebrand
On Wed, 2004-12-01 at 14:58 -0600, Ian Bicking wrote: > Jason Hildebrand wrote: > > Hi Ian, > > > > I'd like to change how the 'http' option is specified. Basically I'd like > > to have this as an AppServer.config option such as "HTTPPort", which would > then > > (via the MiscUtils.Configurable me

RE: [Webware-devel] built-in http server

2004-12-01 Thread Geoffrey Talvola
Another HTTP-related point: I think we ought to make it possible to turn off the regular "adapter" port and ONLY serve HTTP, perhaps by specifying a port of None. Right now, it always listens on the "adapter" port if I'm not mistaken. - Geoff

RE: [Webware-devel] built-in http server

2004-12-01 Thread Geoffrey Talvola
Ian Bicking wrote: > Jason Hildebrand wrote: >> Hi Ian, >> >> I'd like to change how the 'http' option is specified. Basically >> I'd like >> to have this as an AppServer.config option such as "HTTPPort", which >> would then (via the MiscUtils.Configurable mechanism) also be >> available on the

Re: [Webware-devel] built-in http server

2004-12-01 Thread Ian Bicking
Jason Hildebrand wrote: Hi Ian, I'd like to change how the 'http' option is specified. Basically I'd like to have this as an AppServer.config option such as "HTTPPort", which would then (via the MiscUtils.Configurable mechanism) also be available on the commandline (i.e. AppServer --AppServer.HTT

[Webware-devel] built-in http server

2004-12-01 Thread Jason Hildebrand
Hi Ian, I'd like to change how the 'http' option is specified. Basically I'd like to have this as an AppServer.config option such as "HTTPPort", which would then (via the MiscUtils.Configurable mechanism) also be available on the commandline (i.e. AppServer --AppServer.HTTPPort=8080). Does th