It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I have a requirement to develop a VoIP Server (Viber like App). The client software has to be implemented on Android and the server software has to be implemented on .NET.So ,basically, the setup will consist of a server app running on a PC and a wireless access point allowing the clients (Android phones) to connect to the server.Some of the functions I will need for the server side:
Voice transmission
Instant Messaging.
Can anyone help me to implement such a server in .Net?
How much you want to do and what does the server have to do?
The MOST common approach these days is SIP (which is where "know how to read" comes in - that is a public spec, google, RFC, start going, quite long). The good thing is - SIP does not deal with audio at all on the server ;) See, unless you make a audio playback of some sort, noone wants to talk to the server. When I use my phone system, I talk to SOMEONE; not to the server.
SIP deals with SESSION INITIATION - it is a control protocol. The actual audio etc. streams are done via RTP & RTSP - again public protocols, have fun reading (and seriously, they are complex). Unless you NEED the audio streams on the server (recording etc.) there is NO need for the server even to see them - SIP is perfectly fine setting up sessions between two clients directly. SIP is done by MOST (by far) VOIP today. You may use a predefined library. Otherwise you are in a world of quite a lot of debugging, sorry ;)
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
I am interesting to write a C# Client Server application and there are my issues:
1-the client App must be a WinServer
2-the client side, store some files, zipped them and send by http (no TCP or UDP or Socket) to the Server
3-the client side must check the server if the server was offline must be store zip files in some place of local machine and by schedule check the server to start transfer them.
4-the server send some command to client (or client check the server for commands) and need a command execution in client side
5-the client need to check server for some parameters or replace them by default(if server was offline or did not suggest any parameter)
I need some idea about the implementation of this, Does any one have any Idea about it?
I would start with thinking about WCF service in your server application, then have the clients communicate with the server. If you're asking for the all the specifics of how to go about this challenge, I suggest you start with researching WCF and seeing if you can get a basic client/server up and running first, then ask about specific issues.
Then, progress to a WCF host in the client, so the server can communicate back.
Then you can tackle such things as file transfers, offline availability etc.
I've not done this, but this is how I would figure out how to start tackling this.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
How should I go about making an application with C# and .NET where, say, on one computer a button is pressed that triggers an event on the other?
I saw this:
Recommended way to communicate between processes running on different computers on the same network
I've never heard of WCF, is that what I should try?
You're question is way to broad however I can give you a brief overview of how WCF (and most client/server apps) work.
You create a WCF service and then you reference the WCF service (in VS right click references then add service reference) inside your client application. The click in the client application will send a message to the WCF service that will deal with that message.
As mentioned the getting started guides are pretty decent. The WCF Test Client is a great debugging tool as well. If you open the Visual Studio command prompt and type wcftestclient, it will pop up.
Here are some articles that might be helpful:
http://msdn.microsoft.com/en-us/netframework/aa663324.aspx
http://msdn.microsoft.com/en-us/library/dd936243.aspx
http://msdn.microsoft.com/en-us/library/aa751792.aspx
http://blogs.msdn.com/b/tess/archive/2009/01/09/net-hang-my-application-hangs-after-i-called-my-wcf-service-a-couple-of-times.aspx
http://blogs.msdn.com/b/wenlong/archive/2009/07/26/wcf-4-higher-default-throttling-settings-for-wcf-services.aspx
http://merill.net/2008/10/wcf-performance-optimization-tips/
Yes, I would use WCF, because I know it's pretty easy to get a simple project running with WCF, and that will give you confidence to build on it. (Having said that, I dont have much experience with any other networking technologies.)
Start with this Getting Started tutorial.
Then if you have more specific questions, ask them.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
I have create a web site and I need to read data which is created by rfid reader.
this device has some dll which can be use in windows application.
I want to know that is there any way to use those dll in my site in order that I read data from RFID reader? if not is there any way to use that device in web site?
Reading dll's on a clients machine is seen as big security risk and there is not really allowed. It is possible to use ActiveX controls (basically dll's compiled into cab files) which the user can then enable and download, this then will allow you to talk to the ActiveX control which talks to the dll's, which talks to the RFID.
I would rather suggest you use something like Silverlight with out of browser mode, which you can run on the client machine with elevated privilages, then you can talk to com object.
A much better way to go.
ASP.NET application is Server side application with specific security restrictions applied.
So basically, as the question is very generic so my answer too: you can do it, it's enough to be sure that your architecture fits yuor ASP.NET security/permission requirements.
Cause I immagine DLL is kind of COM component where you push signals and read alphanumeric characters specifying your RFID (passive or active) identifier.
Regards.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I am not a socket programmer, but I need to develop a RTSP streaming server in c# .net.
I am developing a blackberry application, but it does not have native video calling support. So to fulfill my requirement, I want to create an intermediate streaming server, that will capture my video data (live bytes) from one BB device, and send it to another BB device. This will be live streaming, just like video calling.
But I have no idea on how to implement it in c# .net. I have tried to google for some code, but didn't get any useful links.
Please suggest if I am not on the right track. I am asking for c# .net as I feel it a bit easier to build for someone newbie like me.
Thanks in advance.
RTSP is going to be a very difficult choice for this. It requires coordinating a TCP control socket and multiple separate channels of UDP data.
You're much better off with any variant of HTTP Video or RTMP or RTMPF. HTTP Video has no single standard--just break up video and send in chunks. Easy. RTMP is used with Flash but can be used separately. There arr sample apps in .NET and Java. RTMPF is also used by Flash but is UDP based instead of TCP and is Peer-to-Peer focused. I think there are also sample implementations available.
Sam
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
I want to make a P2P Chat client, all I want it to do is to be able to send text across to each peer.
I looked at a Chat Client from this example:
http://www.geekpedia.com/tutorial239_Csharp-Chat-Part-1---Building-the-Chat-Client.html
And am wondering if it can be converted to a p2p program?
If so how can it be and can someone provide some code as it will help a lot.
If it can't how can I make a really simple p2p chat program?
Codes and examples will be very helpful.
btw I did look at this article, but it didn't help me:
http://msdn.microsoft.com/en-us/library/ms751502.aspx
I did a similar project once, only using bluetooth rather than Internet.
Mine wasn't chat so much as IM, since it only allowed for two people to converse, but we got it working by using the technique in brydgesk's edit and having the client ('talker') and server ('listener') together in the same application, in such a way that the server only puts out received messages to the local client, rather than rebroadcasting to all connections.
Hope this little bit is helpful, I don't think this is really the right place to help you write the entire application.
For P2P, you need to use UdpClient instead of TcpClient. Google should help you from here :)
Edit: Sorry, I made false assumptions in this answer. If you want to continue using TCP, that's just fine. Instead of creating a separate server application, add the server code to your client application, so that either the sender or receiver acts as the server.
If it is to be done on the intranet, why not use WCF named pipes?