Netty with unix domain sockets

[Trustin Lee (이희승)]

If the peer resides in the same VM, you can use the local transport.
Otherwise, yeah, we need a Unix domain socket transport.  Thanks
Holger for the useful link!

Cheers

— Trustin Lee, http://gleamynode.net/

On Wed, Sep 16, 2009 at 1:28 PM, Utkarsh Srivastava <utkarsh at gmail.com> wrote:
> I was hoping to avoid going through the TCP/IP stack and the extra context
> switch. Still evaluating whether its worth the trouble.
> I didn't quite get what you meant by "strictly 1:1". You can do the usual,
> bind() followed by accept() routine with unix domain sockets as well.
> Utkarsh
>
> 2009/9/15 Holger Hoffstätte <holger.hoffstaette at googlemail.com>
>>
>> Utkarsh Srivastava wrote:
>> > Has anyone been able to setup netty with unix domain sockets? Is it
>> > possible given Netty's APIs?
>>
>> Unix Domain Sockets need native code and are inherently more limited in
>> their interactions as they are strictly 1:1, so it's not really clear to
>> me what you would win. However you could try to adapt the code from
>> http://code.google.com/p/juds/ - it works fine by itself and would be a
>> good starting point.
>> How many thousand local processes do you have? :-)
>>
>> -h
>> _______________________________________________
>> netty-users mailing list
>> netty-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/netty-users
>
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>
>