Author jnoller
Recipients jnoller, ocean-city, pitrou, roudkerk, trent
Date 2008-08-08.14:28:47
SpamBayes Score 0.000110309
Marked as misclassified No
Message-id <1218205752.85.0.278421858389.issue3270@psf.upfronthosting.co.za>
In-reply-to
Content
Trent/Antoine - I'm stuck on the fence about this. Per trent's own 
suggestion - removing the allowance for the 0.0.0.0 style address means 
that the self._address is always a connectable end-point: this provides 
clarity to the API.

However - to Antoine's point - using 0.0.0.0 to listen on "all 
addresses" is actually pretty common, especially when working with 
bigger servers (which generally have multiple cores). Using the 0.0.0.0 
address makes it easy to say "listen everywhere" - where, in the case of 
a Manager is actually very useful (you could have processes connecting 
to a Manager on a machine from different networks).

Attached is a cleaned up diff of the removal of the fqdn call - this 
should resolve the original problem while leaving the door open for the 
ability to connect to the 0.0.0.0 "address".

I need someone with a windows machine (Hi Trent!) that exposed the 
original problem to test the patch. Currently I'm favoring this rather 
than locking out the 0.0.0.0 option.
History
Date User Action Args
2008-08-08 14:29:13jnollersetrecipients: + jnoller, pitrou, ocean-city, roudkerk, trent
2008-08-08 14:29:12jnollersetmessageid: <1218205752.85.0.278421858389.issue3270@psf.upfronthosting.co.za>
2008-08-08 14:28:50jnollerlinkissue3270 messages
2008-08-08 14:28:48jnollercreate