[Mono-dev] Non-TCP/IP socket access
andyhume32 at yahoo.co.uk
Thu Aug 4 06:58:26 EDT 2011
> -----Original Message-----
> From: mono-devel-list-bounces at lists.ximian.com
> [mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf
> Of Andy Hume
> Sent: 27 July 2011 22:47
> To: 'Robert Jordan'; mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-dev] Non-TCP/IP socket access
> > -----Original Message-----
> > From: mono-devel-list-bounces at lists.ximian.com
> > [mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf
> Of Robert
> > Jordan
> > Sent: 25 July 2011 15:27
> > To: mono-devel-list at lists.ximian.com
> > Subject: Re: [Mono-dev] Non-TCP/IP socket access
> > On 25.07.2011 15:24, Andy Hume wrote:
> > > Currently other socket types are blocked. This occurs
> > They are really blocked on purpose, but this is not set in stone.
> > You could, for example, provide patches that, for unknown (but not
> > limited to) AFs, simply assume that the specified sockaddr
> is of the
> > generic type "struct sockaddr_storage"
> > (see RFC 2553). All Unixes (including OSX) and even Windows support
> > this type.
> > What we'd need is a platform dependent SocketAddress to
> > sockaddr_storage mapping in the runtime.
> OK. Please find a patch attached. :-) Works well for me. I
> think it's as you foresaw; use of sockaddr_storage and all...
So what's the best way to progress this? :-) Is there something I can
do? CC the people who've worked on sockets perhaps?
More information about the Mono-devel-list