Hello colleagues.
Today, I was thinking of some ideas and I decided to try to develop a simple alternative to Remote Desktop. By meaning simple, I want to say, it will be for me only and it will have basic functions - to be able to download a particular file from home when I connect to my pc, to get screenshot of the desktop, because sometimes my brother uses my computer and I want to have control over everything. Another, perhaps known functions for one remote desktop software - delete file, file, directory info and this is all I think. Of course some structure of the directories and files. Because I have basic experience with communication technologies, I realized that my scheme will die soon, because I am behing a router and I have to open ports. Moreover, one day it can be big enough to be sold(let's first reach this day
). That is why, I am asking about the way of developing communication. I do not want to use direct sockets anymore, because I made one simple chat application and from there a realized how limited are they for people behind routers. I am thinking of the idea to build a centralized server, so that both the server module, which is installed on the pc, that is sharing the resourses and the client module that is connecting to the server module are using this centralized server for reaching each other.
Because I do not have experience exactly with this way of development, I am asking you if it is a good way to solve the task, or I should use something else. I would like to here comments about the way with the centralized server or maybe another suggestions.
Regards, Penko.
Edit: I have heard of some ways of communication but I do not know the difference between some of them
- Sockets(well-known), .NET Remoting(Nothing), Web Service(Basic).
This post has been edited by pe_mitev: 23 Sep, 2008 - 11:13 AM
| 