Date: Sun, 11 Jan 2009 16:22:38 +0000 From: "Bruce M. Simpson" <bms@FreeBSD.org> To: Attila Nagy <bra@fsn.hu> Cc: Adrian Chadd <adrian@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, Robert Watson <rwatson@freebsd.org>, Julian Elischer <julian@elischer.org>, svn-src-head@freebsd.org Subject: Re: svn commit: r186955 - in head/sys: conf netinet Message-ID: <496A1CCE.90701@FreeBSD.org> In-Reply-To: <4968E8B4.9090309@fsn.hu> References: <200901091602.n09G2Jj1061164@svn.freebsd.org> <4967A500.30205@fsn.hu> <4967B6D9.90001@elischer.org> <4967C539.2060803@fsn.hu> <d763ac660901091411x40eb8084v134f0ab2189afddb@mail.gmail.com> <49686A30.4000205@fsn.hu> <alpine.BSF.2.00.0901101026220.16794@fledge.watson.org> <d763ac660901101012icb544b1v3ff940bd39f1abb6@mail.gmail.com> <4968E8B4.9090309@fsn.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
Attila Nagy wrote: > ... > Do you know anything else which can do that now with an easy API > (accessible from high level languages like perl or python)? I sent a patch to the Python guys to implement the protocol-independent multicast socket API a good while back. It takes a long time to get feedback unless you're "in the loop" with the current development version of Python and know the developers. Adding support to Python for socket options itself isn't terribly difficult -- the socket module is reasonably lightweight C glue code -- it just takes time to jive with their development process, it seems. Having said that, their reference platform(s) already implement these particular socket options, so I guess it may just be down to lack of interest/time, which does happen... cheers BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?496A1CCE.90701>