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

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.

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.

extending the brickd would be great! AuronX' idea is also nice!

thanks