Architecture: Notes on board specific networking implementations #4990
Replies: 1 comment
-
Posted at 2015-09-25 by @gfwilliams Hi, It'd be really helpful if that document was in GitHub or something like a Gist - then it could easily be added to?
Yes. It's in the existing documentation i keep pointing you at:
Yes - just close after everything has been sent (even if there is now received data)
Again, in the docs
And: It's more of a hack for CC3000 and you can ignore it. In the CC3000 the whole thing may spontaneously crash. checkError allows the CC3000 code to check for this and if there's a problem to attempt to restart it before anything is done in the socket library.
It's 0 - but just not writing the return value is enough. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2015-09-24 by Kolban
As the port of Espruino to a particular board continues, a lot of questions have come up on implementing the board specific portion of the networking functions. To attempt to understand this area better, a first pass at a document has been written that attempts to describe the board specific functions. This document will be elaborated on over time and eventually submitted to the Espruino project when the porting project has completed.
Attachments:
Beta Was this translation helpful? Give feedback.
All reactions