Eventmachine talk - Jul 2008 - local source port/address bind()ing

From: "Roger Pack" <roger.pack at
leadmediapartners.com>
>> From: "Eric Monti" <emonti at matasano.com>
>>
>>> We may need to submit patches.
>>>
>>> In a somewhat similar situation (discussed on this list back in
April),
>>> it turns out to be possible to have EM create a TCP server on an
>>> ephemeral port--but no way to determine what that port number is.
>>
>> iirc that patch went in.
>
> Indeed it did. get_sockname() has been exposed since 0.12.0.
Oh -- excellent.

Oddly it seems get_sockname existed several months *prior*
to the April thread discussing ephemeral ports.  (lol?)


Regards,

Bill

On Jul 16, 2008, at 8:35 PM, Bill Kelly wrote:
>
> From: "Roger Pack" <roger.pack at leadmediapartners.com>
>>> From: "Eric Monti" <emonti at matasano.com>
>>>
>>>> We may need to submit patches.
>>>>
>>>> In a somewhat similar situation (discussed on this list back in
>>>> April),
>>>> it turns out to be possible to have EM create a TCP server on
an
>>>> ephemeral port--but no way to determine what that port number
is.
>>>
>>> iirc that patch went in.
>>
>> Indeed it did. get_sockname() has been exposed since 0.12.0.
>
> Oh -- excellent.
>
> Oddly it seems get_sockname existed several months *prior*
> to the April thread discussing ephemeral ports.  (lol?)
I think I first saw it in svn... right after i''d implemented a patch
of my own that was almost verbatim the same and wanted to see if I
should submit it :)

In general, I think exposing more of the lower socket functionality is
definitely a good thing for EventMachine, and one I think we''ll
inevitably see more of out f necessity.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2421 bytes
Desc: not available
URL:
<http://rubyforge.org/pipermail/eventmachine-talk/attachments/20080717/69696864/attachment.bin>

>>
>> Indeed it did. get_sockname() has been exposed since 0.12.0.
>
> Oh -- excellent.
>
> Oddly it seems get_sockname existed several months *prior*
> to the April thread discussing ephemeral ports.  (lol?)
I believe that get_sockname for client sockets has existed for awhile.
 Which, come to think of it, does show you the port for an ephemeral
port.  The ability to use it for server [acceptor] descriptors was
introduced around the time of 0.12.0. I''m not sure if it was right
before or after. IIRC.
=R