Hi Miika,
On May 4, 2013, at 8:54 AM, Miika Komu wrote:
> with connected sockets, (almost) the same API calls could be used and
> the details could be possibly abstracted away (some kind of a flag still
> needed to choose between TCP and UDP). A number of applications appear
> to support both
Hi Itamar,
On 05/04/2013 05:00 PM, Itamar Turner-Trauring wrote:
> On 05/04/2013 07:28 AM, Miika Komu wrote:
>> Howdy,
>>
>> we investigated the networking APIs of Twisted (10.2) and published our
>> findings in Ottawa Linux Symposium 2012:
>>
>> http://nw.dreamhosters.com/ols/ols2012/ols2012-komu
On 05/04/2013 07:28 AM, Miika Komu wrote:
> Howdy,
>
> we investigated the networking APIs of Twisted (10.2) and published our
> findings in Ottawa Linux Symposium 2012:
>
> http://nw.dreamhosters.com/ols/ols2012/ols2012-komu.pdf
Thanks for sending us your suggestions for improvement. I'm wondering
Hi,
On 04/05/13 14:28, Miika Komu wrote:
> Security issues
> ---
> * R1.3: IPv6-mapped addresses should not be present on the wire for
> security reasons.
> * R3.2: Server-side multihoming for UDP does not work properly. The
> framework should use SO_BINDTODEVICE option or sendmsg()/
Howdy,
we investigated the networking APIs of Twisted (10.2) and published our
findings in Ottawa Linux Symposium 2012:
http://nw.dreamhosters.com/ols/ols2012/ols2012-komu.pdf
We propose two types of improvements to the framework described in full
detail in section 4.3.1 of the publication. Firs
