In fact, this implementation is not a true sense of video communication, neither Peer-to-peer nor very high performance, because basically two clients at the same time to the server to deliver video information, and then by the server to relay to each other.
The point is two.
IIS root decentralization clientaccesspolicy.xml files
Note the amount of data defined in the service is 2147483646, or it may not pass
This is a one-way client. Periodically passing data streams with chat identities to the server
[DataContract]
public class Uservideo
{
[DataMember] public
string UserName {get; set;}
[DataMember]
public string Partnername {set;
[DataMember]
Public byte[] Videobyte {set; get;}
}
There are only two service contracts, one for storing video streams and one for streaming video.
[ServiceContract]
Public interface Ichatservice
{
[operationcontract]
void Sendvideo (Uservideo uservideo);
[OperationContract]
List<uservideo> Getvideos (String username,string partnername);