I was hoping to avoid going through the TCP/IP stack and the extra context switch. Still evaluating whether its worth the trouble.<div><br></div><div>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.</div>
<div><br></div><div>Utkarsh</div><div><br><br><div class="gmail_quote">2009/9/15 Holger Hoffstätte <span dir="ltr"><<a href="mailto:holger.hoffstaette@googlemail.com">holger.hoffstaette@googlemail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Utkarsh Srivastava wrote:<br>
> Has anyone been able to setup netty with unix domain sockets? Is it<br>
> possible given Netty's APIs?<br>
<br>
</div>Unix Domain Sockets need native code and are inherently more limited in<br>
their interactions as they are strictly 1:1, so it's not really clear to<br>
me what you would win. However you could try to adapt the code from<br>
<a href="http://code.google.com/p/juds/" target="_blank">http://code.google.com/p/juds/</a> - it works fine by itself and would be a<br>
good starting point.<br>
How many thousand local processes do you have? :-)<br>
<br>
-h<br>
_______________________________________________<br>
netty-users mailing list<br>
<a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
</blockquote></div><br></div>