2 replies to this topic

[teknix1]

Well looks like my luck hasn't been too good lately. I seem to be crossing a few issues implementing my own http server. The latest is a blocking socket read way down in onw of the framework libraries. Luckily enough this bug has already been solved over at TinyCLR (http://www.tinyclr.c...page=3#msg53484). Unfortunately, my only solution is to rebuild my own firmware and that is not an option right now, because of another problem I am pursuing with the ContentLength64 property of the response object. That one only occurs with GCC built firmwares.

 

Has anybody stumbled across this issue? I'd like to hear about your solution to this if possible.

 

Thanks in advance!

Nic

[NeonMika / Markus VV.]

I have to go to university now, but at least I can give you the advice to look at my werbserver code (or even use it )

I'm not sure if it helps you becaue I worked with Sockets, because I didn't want to have to abstraction layer (and overhead) the HttpListener would have had.

 

Greets, Markus

[teknix1]

Thanks Markus,

 

I will definitely have a look.

 

I since realized the bug is not a piece of code that gets embedded in the firmware, so I was able to rebuild that assembly and include it in my project. Works better but as always, I fix one bug and I find another one... I think I'm going to end up making a solution with all of the .Net Micro Framework projects and reference those so I can debug and step through. I haven't found the correct way to do that.

 

Thanks

Nic