It's not great right now, but it does work - if not as efficiently as it could. I think getting ESP8266 actually working reliably with hardware peripheral support should really a priority before you start optimising.
Right now the API is the way it is because it's easy and pretty efficient on 'normal' Espruino platforms - it's also a bit like a normal socket layer so it won't totally throw people. We could definitely add some kind of data_received and get_data_to_send callbacks at some point, but I'd want to make really sure they weren't overly complicating the existing stuff just for the sake of ESP8266, and that any changes got tested properly on Espruino hardware and CC3000/WIZnet/etc first.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Yep, I agree with you both here.
It's not great right now, but it does work - if not as efficiently as it could. I think getting ESP8266 actually working reliably with hardware peripheral support should really a priority before you start optimising.
Right now the API is the way it is because it's easy and pretty efficient on 'normal' Espruino platforms - it's also a bit like a normal socket layer so it won't totally throw people. We could definitely add some kind of
data_received
andget_data_to_send
callbacks at some point, but I'd want to make really sure they weren't overly complicating the existing stuff just for the sake of ESP8266, and that any changes got tested properly on Espruino hardware and CC3000/WIZnet/etc first.