quot; <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Thursday, April 19, 2001 4:21 PM
> Subject: Re: [Zope-dev] Zope options order sensitive
>
>
> > The example was fictional; the ips and ports have been changed to protect
> > the guilty. I'm more
TED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, April 19, 2001 4:21 PM
Subject: Re: [Zope-dev] Zope options order sensitive
> The example was fictional; the ips and ports have been changed to protect
> the guilty. I'm more interested in just understanding how the code works.
>
> I
On Thu, 19 Apr 2001, Chris McDonough wrote:
> Not really... do you want to only listen on 127.0.0.1?
>
> - Original Message -
> From: "Chris Gray" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 19, 2001 3:43 PM
>
Not really... do you want to only listen on 127.0.0.1?
- Original Message -
From: "Chris Gray" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 19, 2001 3:43 PM
Subject: [Zope-dev] Zope options order sensitive
>
> I'm just begi
I'm just beginning my study of the zope source. Going through z2.py I
noticed that order matters in specifying command line options.
For instance: ./start -a 127.0.0.1 -P 8000
sets HTTP_PORT to: [('127.0.0.1', '8080')]
but:./start -P 8000 -a 127.0.0.1
sets HTTP_PORT to:
