Click here to Skip to main content
Sign Up to vote bad
good
See more: C#
hi again,
 
im now involved in a project for developing a server and client application in which a video file from server side is to be displayed in all the client side applications (multiple clients at a time).
 
so it should work like 2 windows open in the server and client computers and the video should run within both the server and client window forms.
 
any help ???
Posted 17 Jan '13 - 6:35

Comments
Sandeep Mewara - 17 Jan '13 - 12:40
And you tried anything of what you plan to implement.
kiran131993 - 18 Jan '13 - 13:30
i have implemented the desktop sharing technique and now want to stream video files alone in a form
David_Wimbley - 17 Jan '13 - 12:44
what exactly do you need help with? logistics of client server and how that works? how to stream a file in c#? how to open 2 windows at once? If you can provide some clarification im sure youd get a better response
kiran131993 - 17 Jan '13 - 12:46
k i need to know abt how to send the video from server side and how to receive it in the client side. also wat protocol that i can use.
David_Wimbley - 17 Jan '13 - 12:49
Another question to further clarify, is this winforms/wpf/asp.net? I see you said window forms but what to double check as client side could include a browser as well.
kiran131993 - 17 Jan '13 - 12:51
i want to do it in windows forms. and not to open a webpage and all. just run the forms on both sides and show the video played.(more kind of like a seminar session but not live but pre-recorded)

1 solution

First you need to tell us what you did until now. What type of video you have now and ...
 
But about your question you need to convert images or video source to an acceptable video format. Using FFMPEG or something like that.
But if you have video file in an acceptable format already you can ignore above line
.
Then you need to send data to client(s). For doing so you need to learn socket programming or you need to use a library. Two famous streaming protocols are:
http://en.wikipedia.org/wiki/Microsoft_Media_Services
http://en.wikipedia.org/wiki/Real_Time_Messaging_Protocol
 
These links may help you for implementing RTMP in your app:
http://www.live555.com/liveMedia/
Managed Media Aggregation using Rtsp and Rtp
http://net7mma.codeplex.com/
http://www.streamcoders.com/
 
Or you can write your own protocol completely from ground and actually I recommend it because it is easier to learn socket programming then using MMS or RTMP Smile | :)
 
Then in your client app you need to render video. You can use a user control or you can use Direct2D to show video to user. But this is an other topic.
  Permalink  
Comments
SoMad - 20 Jan '13 - 15:41
I would not recommend OP writes his own protocol. If this is supposed to run in different network environments, there is a good chance network administrators will resist it and in many organizations, their word is the law. Stick with standardized protocols. RTP can be a pain to get fully integrated, but it is a well established protocol with support for proxy servers, which is something that can also make or break the application being accepted by a network administrator. Soren Madsen
Soroush Falahati - 20 Jan '13 - 17:32
Yeah. You are correct. But he can write it's own protocol based on HTTP protocol and it will solve any problem. The main reason that I said, writing it him-self is better, is simplifying of protocol. He will get rid of lot of difficulties that come with RTMP. But any way every thing depends on him.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Your Filters
Interested
Ignored
     
0 Sergey Alexandrovich Kryukov 518
1 Arun Vasu 315
2 Maciej Los 218
3 OriginalGriff 205
4 Aarti Meswania 170
0 Sergey Alexandrovich Kryukov 9,670
1 OriginalGriff 7,409
2 CPallini 3,968
3 Rohan Leuva 3,352
4 Maciej Los 2,861


Advertise | Privacy | Mobile
Web03 | 2.6.130523.1 | Last Updated 20 Jan 2013
Copyright © CodeProject, 1999-2013
All Rights Reserved. Terms of Use
Layout: fixed | fluid