[Twisted-Python] Re: Using FQDN with transport.write calls...

Tim Allen screwtape at froup.com
Sun Aug 13 17:23:09 EDT 2006

On 14 Aug 2006, at 06:38, Chaz. wrote:
>>> Jean-Paul Calderone wrote:
>>>> On Sun, 13 Aug 2006 07:28:51 -0400, "Chaz."  
>>>> <eprparadocs at gmail.com> wrote:
>>>>> My application requires that I use FQDN in place of the normal  
>>>>> IP addresses in transport.write calls.
>>>> No it doesn't.  What behavior would you expect this to provide  
>>>> which you
>>>> desire in your application?
> Sorry for the top-post. What I want to do is the following
> 	self.transport.write(data,('www.foobar.com',6000))
> I think that says it succinctly.

I think that Jean-Paul was trying to say something like this:  
"self.transport is a file-like object, so its write() method takes  
only data. It wouldn't make sense to supply an IP address and port to  
sys.stdout.write(), why do you expect that self.transport.write()  
would accept one?"

More information about the Twisted-Python mailing list