[bind10-dev] [svn] commit: r1223 - in /branches/jinmei-asio: ./ src/bin/auth/ src/bin/loadzone/ src/lib/auth/ src/lib/cc/ src/lib/config/ src/lib/dns/ src/lib/dns/rdata/generic/ src/lib/dns/tests/ src/lib/python/isc/auth/ src/lib/python/isc/cc/ src/lib/python/isc/config/ src/lib/python/isc/config/unittests/

Danny Mayer mayer at gis.net
Sun Apr 18 03:24:56 UTC 2010


Jeremy C. Reed wrote:
> On Mon, 8 Mar 2010, JINMEI Tatuya / ???? wrote:
> 
>>>> adapted command channel module with boost::asio.  ugly hack, but works.
>>> What does this mean for the BIND 10 admin? Now using Unix domain 
>>> sockets? Is it an optional?
>> Basically, nothing.  This change basically provides the same
>> functionality with a different tool.  A possibly non-obvious
>> consequence, however, is that BIND10 may now magically work with
>> Windows:-)  Because ASIO supports Windows.  In reality I'm not that
>> optimistic though.
> 
> Does the ASIO support Unix domain sockets? I understand on Unix we plan 
> to be able to use those (so we can use Unix file permissions for 
> security).  (I understand that Windows has a different but similar 
> functionality to domain sockets.)
> 

A little late, but no Windows doesn't have anything similar to Unix
domain sockets. It does have the capability of applying permissions to
objects like pipes but it's not clear from this comment what you are
trying to do with the socket or what permissions you are trying  to
apply to the socket. You can however emulate most api's to accomplish
similar functionality as long as they can be fully and clearly defined.

Danny





More information about the bind10-dev mailing list