It is just a preliminary idea. Recently, the open API development kit of Skype was used by developers. ProgramCommunication, or even full control over the Skype interface. A few days ago, I saw a foreigner using the excellent point-to-point communication function provided by the Skype API to add the network combat function for his games. I suddenly wondered that Skype's P2P technology should be world-leading, since it has opened APIs, we should be able to create a communication channel similar to socket, TCP, or HTTP Based on Skype. This network transmission channel is equivalent to an underlying network interface, many applications that require network interconnection can communicate over this Skype channel.
Now, back to the remoting technology I was familiar with, remoting currently has two channels available: HTTP and TCP, but Microsoft provides an extension mechanism to allow developers to customize communication channels. In the past, we saw a foreigner using MS message queue to implement a custom transmission channel on the codeproject website. In theory, we can also provide a transmission channel for remoting through Skype, of course, it is P2P, and any intranet application can communicate directly.
Of course, the above idea is just a preliminary idea. In the next step, I will try to implement such a demo. P2P is undoubtedly attractive, but there are also some fatal defects, that is, the final application must use Skype to work. It seems that there are no commercial applications with this working model yet ?! A program must use other programs to work ?!
Before starting the action, I should sum up myself. I feel that this is a spark of a collision. The following many factors have come together to create a strange idea. Haha, I am so intoxicated :)
1. Skype P2P
2. Skype open API
3. Online Combat games developed by foreigners using Skype APIs
4. Distributed Computing remoting technology, HTTP and TCP transmission channels
5. Custom transmission channels in remoting
6. Custom channels created by foreigners using MS message queues