lipp Geschrieben May 30, 2012 at 16:21 Share Geschrieben May 30, 2012 at 16:21 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 Zitieren Link zu diesem Kommentar Share on other sites More sharing options...
AuronX Geschrieben May 30, 2012 at 20:45 Share Geschrieben May 30, 2012 at 20:45 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. Zitieren Link zu diesem Kommentar Share on other sites More sharing options...
borg Geschrieben May 30, 2012 at 21:19 Share Geschrieben May 30, 2012 at 21:19 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. Zitieren Link zu diesem Kommentar Share on other sites More sharing options...
lipp Geschrieben May 31, 2012 at 10:50 Autor Share Geschrieben May 31, 2012 at 10:50 extending the brickd would be great! AuronX' idea is also nice! thanks Zitieren Link zu diesem Kommentar 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.