Closed chkr1011 closed 6 years ago
@JanEggers I tried to implement the mentioned enum but I saw that it is not that easy. Then I tried to remove the RAW stream and always use the regular one. So also with the BufferedStream as the wrapper stream. I didn't get any errors with the TestApp.NetCore which also uses the BufferedStream. Both client and server are running perfectly. A ESP client is connected, sending data and also the UWP test app is connected with the server. So can you share some details how to reproduce the issues with the BufferedStream which requires the approach with the Raw-Stream access?
if it is running fine now then remove the raw streams. the issue was that the connect package was not received on either netcore or netfx because the buffered stream tried to read buffersize bytes and blocked but until the connect message is processed there where no further messages/bytes = deadlock. it may be possible that the issue i expierienced was one of the other issues we fixed while developing v2.5
OK I will push my changes. Can you please check it with a quick test. I also ran several tests and it seems to work without any issues. I will now test it with an encrypted connection with Azure IoT Hub. If this works I tested all possible scenarios. And please check my code fur sure 😄
Version 2.5 is now released! Thanks to everyone who has contributed!
I want to release a new version soon because we have lots of new features. Before doing this I want to summarize the open topics: