The SPI issues were at the JavaScript API level, and CC3000/WIZnet are one step lower than that - so there shouldn't have been an issue.
I know about the GET issue on WIZnet (it was reported elsewhere) - it's because it's trying to find a free 'socket'. The WIZnet chip has 8, and they should be free after a GET completes. Did you do the GETs in quick succession? I was pretty sure I tested it, but I probably did so with maybe a minute between each GET - with that kind of delay the socket probably would have timed out and returned to its original state.
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.
The SPI issues were at the JavaScript API level, and CC3000/WIZnet are one step lower than that - so there shouldn't have been an issue.
I know about the GET issue on WIZnet (it was reported elsewhere) - it's because it's trying to find a free 'socket'. The WIZnet chip has 8, and they should be free after a GET completes. Did you do the GETs in quick succession? I was pretty sure I tested it, but I probably did so with maybe a minute between each GET - with that kind of delay the socket probably would have timed out and returned to its original state.