avword

It's all kind of moot unless the netduino has both the code (firmware) and the hardware to support taking in the power.

(Although I think it would be a cool feature to have!)

No firmware or hardware needed...

I think everyone is misunderstanding my link. The device I posted extracts power from an powered ethernet line and then converts it to one of the voltages for powering devices that don't support POE.
The netduino has a 7.5 - 12 VDC power input in the lower left the unit. The trendnet device has a power output. Run a cable from the trendnet power output to the power input on the netduino.

• Splits power and data from a single Ethernet cable into two separate sources
• Use this with a TRENDnet PoE switch to power and network a non Power over Ethernet device
• Save on installation and equipment costs

POE is way different in voltage specifications then required by the netduino, it is designed to deliver 15watts or more at 44 to 57 volts. So way past the 12v max for netduino.

Not to say someone could come with a inline tap that could bring it down to something reasonable.

Did you look at that link? The trendnet device that I linked to features:
Supports Adjustable Output 5V, 7.5V, 9V, 12V

It will be nice to power the board through Power Over Ethernet.
It's an important feature that I really need on my domotic project, is it plane ?

Try this out:
http://www.trendnet....TPE-102S&cat=58

The SocketServer sample which was installed with the .NET Micro Framework 4.1 SDK has a multi-threaded socket server sample... It could be implemented in a simpler fashion, but that should give you a start...

[If in case you're not familiar with multi-threading, we or someone in the community could maybe create a simpler sample as well.]

Chris

Ok cool, I see the example program (I didn't know those were there). I'll play around with that for a bit. From what I see so far, it makes sense. I see that it also shows how to end the session if the connection was closed or reset.

That said, if you or someone in the community had the time, I think a general multi-threading example would be very useful (but only if you have the spare time).


Thanks!!

If you run the .Accept(...) function again, you should be able to accept multiple clients.



First thoughts... When you get a new connection, perhaps you can create a new thread and service that connection (socket) from the new thread...and then set timeouts and catch exceptions if/when the socket times out...

Chris

Right now .Accept is getting run again as it is in the first "while(true)" loop. So what happens is that after the first client disconnects (by pressing "c"), the second client is serviced. But until the first client disconnects, the second one is in a hung state. Could you point me to an example of how do each connection as a separate thread?