BIND 10 #111: setting alternative msgq-port fails

[BIND 10 Development]

#111: setting alternative msgq-port fails
--------------------------+-------------------------------------------------
 Reporter:  jreed         |        Owner:  each    
     Type:  defect        |       Status:  assigned
 Priority:  major         |    Milestone:          
Component:  Unclassified  |   Resolution:          
 Keywords:                |    Sensitive:  0       
--------------------------+-------------------------------------------------

Comment(by jelte):

 i was working on using domain sockets for msgq on friday and noticed that
 the ASIO code for c++ clients (lib/cc/session.cc) had a hardcoded port
 number, which most probably causes this :)

 (the domain socket file is a bit less hardcoded, though having it
 completely overridable is still a todo for me, since that requires an api
 change somewhere, but i want to look at that today, currently it is
 overridable by an environment variable)

 If so, I propose to let this ticket go and focus on mine getting done,
 reviewed and merged (ticket #183)

-- 
Ticket URL: <https://bind10.isc.org/ticket/111#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development