- I want it to work on windows servers.
- This will be a cloud type server - it will consist of modules / parts working on different machines around the world, using http \ tcp + upnp to connect to each other
- On each machine \ monitoring \ monitoring modules will be monitored to provide performance statistics.
- This network will work with a lot of streaming data. VIDEO \ AUDIO \ data transfer
- He is going to use FFMPEG for re-encoding and OpenGL, OpenCV and such for filtering (.NET shells exist and BTW work)
- He will not use WCF or IIS
- I want to develop it in a team of 2-4 developers, smart students.
Is it good to create this in C # .Net, or will I not spend my time promising the ease that it can provide the developer and switch to C \ C ++?
So is it wise to write a server application in C # in my case?
Offtop - why not WCF
Warning: there is an opportunity subjectively.
WCF is the lattice when you have a large enclosure with relatively little data exchange in a single maintenance session.
When you have a video, LIVE video, things get more complicated. A large amount of data, many users simultaneously download and exit your service.
http- - , , WCF - , way2much - WCF? - - , + - Silverlight + IIS, , Silverlight\WindowsMediaPlayer, .
. ( - ) Silverlight + IIS + WCF. , - , , FLV Flash, -. , , , MS .
Flash FLV , FLV ( FLV- FLV "TAG", : , -, , ..), Flash ! \ . , \. TAG \.
, , WCF - , , .
, WCF .
2009 2010 WCF, , silverlight flash, \, . -, , . , , , , .
WCF - , , \.
FFmpeg\OpenCV C, , ... C... Linux...
.Net ( Tao.FFmpeg), , # Marshal 2 C- ( ) .. , Emgu CV, ...