lipp Posted May 30, 2012 at 04:21 PM Share Posted May 30, 2012 at 04:21 PM hello! thank you for providing the TCP/IP spec! i'd really prefer to have the brickd provide 2 sockets - one for "calls" (request/response) - one for "events/callbacks" (response) this would make logic much easier, when dealing with a single threaded environment (using blocking ops for "calls", and async io for "callbacks")! regards Quote Link to comment Share on other sites More sharing options...
AuronX Posted May 30, 2012 at 08:45 PM Share Posted May 30, 2012 at 08:45 PM I believe the brickd keeps track of the connections requesting events. If so you could simply open two connections and register your callbacks only on one of the connections. Then the events/callbacks should only occur on that connection. Quote Link to comment Share on other sites More sharing options...
borg Posted May 30, 2012 at 09:19 PM Share Posted May 30, 2012 at 09:19 PM We can't do this in general because the WIFI Extension won't be able to do this efficiently (utilizing two sockets). It would be possible to make this behavior configurable for brickd, i suppose. Quote Link to comment Share on other sites More sharing options...
lipp Posted May 31, 2012 at 10:50 AM Author Share Posted May 31, 2012 at 10:50 AM extending the brickd would be great! AuronX' idea is also nice! thanks Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.