Having spent several days trying to get a reliable Http server running on a Raptor and trawling every single post about networking issues (wrapper classes and execution constraints etc) it seems very clear that the current NetMF 4.3 networking stack and / or the ENC28 drivers are in no way capable of supporting a commercial application.
Without asking for solutions the issues are based around the well reported Socket.Accept() method blocking indefinitely, a similar less frequent issue with Socket.Send() and a general instability in the networking stack. At very low ‘stress’ levels it’s possible to keep everything running for hours (and maybe days) at a time but trying to serve larger amounts of data and / or more frequently very quickly introduces issues.
I know the request will be for me to show some code snippets so that someone can work out what I am doing wrong but I am 100% confident that it’s very simple C# socket code and I have tried many ways around the problem (ExectutionConstraints, thread wrappers, ThreadPools, bandwidth throttling, switches, hubs, crossover connections, no firewalls, better cables, different mainboard sockets, different SPI clock speeds etc) and the problems remain.
You can improve the situation by sending very small packets of data at a time (this cuts down the number of Socket.Send hangs) but the Socket.Accept() issues are random and unpredictable.
My question isn’t how to fix the problem directly but whether the ‘talked about’ improvements in NetMF 4.4 are likely to have any effect on these issues and if yes, on what time scale can we think about (not expect!) a GHI rollout of 4.4 compatible firmware.
I am evaluating the board for a commercial project and honestly it’s a show stopper right now so any guidance would be very gratefully received. The very helpful community on here is, in many ways great, but it also very much blurs the picture as there are so many conflicting answers to different problems and rumours about what someone heard might be happening.
GHI clearly have to take care of their commercial interests and are busy developing new stuff which is great but the bottom line remains (it really does, whatever anyone may think) that issues like this flaky network stack are a genuine, major issue for many.
This is not meant to start a war of words, I am simply after some clarity on the situation as I will need to look to other platforms very soon if there is no light at the end of the tunnel.
Thanks and regards,