So just to clear up: For the 1v62 release I did some work on WIZnet - specifically improving the HTTP server stability and making sure that using setIP didn't mess up the Mac address - hopefully this will have really helped @Pat's problems.
There's still:
HTTP GET with DNS (eg, not to an IP) seems to be unreliable
HTTP GET doesn't seem to free sockets properly
HTTP server can get swamped and will stop working if you spam it with loads of requests at once
WIZnet have offered to look into those so I'm just waiting for their response.
I'm not saying this is a WIZnet chip issue or a problem with their code. I'm sending 'closesocket' requests to the WIZnet chip and the socket state isn't changing to 'closed'. It's probably unread data or something and I fully expect WIZnet to know what the problem is within a few minutes - so as being as they offered the help, I'm taking them up on it :)
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.
So just to clear up: For the 1v62 release I did some work on WIZnet - specifically improving the HTTP server stability and making sure that using
setIP
didn't mess up the Mac address - hopefully this will have really helped @Pat's problems.There's still:
WIZnet have offered to look into those so I'm just waiting for their response.
I'm not saying this is a WIZnet chip issue or a problem with their code. I'm sending 'closesocket' requests to the WIZnet chip and the socket state isn't changing to 'closed'. It's probably unread data or something and I fully expect WIZnet to know what the problem is within a few minutes - so as being as they offered the help, I'm taking them up on it :)