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 proposing that the command line argument goes away, and HTTPPort
> defaults to None, so you _have_ to specify HTTPPort in your config file in
> order to get HTTP.
You're correct, but I changed my mind -- see the other post I just sent.
> If so, I like it. This also solves the problem of how exactly you are
> supposed to get HTTP if you are running as a Windows Service, in which case
> there are no command line arguments... (I had to do it by inserting a
> horrible hack into the source code).
Me too. This is part of what I'm trying to fix. :)