This is a discussion topic not a business offering, it's for discussing features and other topics regarding the TVAI think it should appear in The Business Forum
But the Forum Discussion is for discussing the functions of this forum and ways to improve it.This is a discussion topic not a business offering, it's for discussing features and other topics regarding the TVA
Hi,Yes they are under heavy load because it receives and sends the texts, gestures, device layout changes and more.
HelloHi,
I have purchased the source code, but not had a chance to look everything over.
So, the above statement is confusing to me because I thought that the backend is only used to initiate an initial hand-shake, then a direct connection is established between the two clients from that point on, so a backend "server" is no longer needed for that session anymore.
If this is not an accurate understanding of the system, then is there a "System Description" document available that explains the different parts of the system and what each part does?
You could transmit the input transfers through the JRDC2 but we wouldn't recommend it because you will stress the server Unless you have a really good VPS server.Hi,
VNC is an open-source protocol for remote control. From what I understand, all the input/screen changes are handled directly between the two clients after a connection is established, so server load is reduced to zero after the connection is made between the clients.
I would be interested in knowing what your dev team thinks about the use of this VNC protocol to help increase the efficiency of your product.
Here is some more info on VNC:
I am confused. I was recommending if your dev team would be interested in using the VNC protocol so that nothing will have to go through any server after the two clients are connected to each other. This way it reduces the load to the server by 100% and eliminates the additional propagation delay of all inputs and screen changes having to first go through a server before reaching the other client.You could transmit the input transfers through the JRDC2 but we wouldn't recommend it because you will stress the server Unless you have a really good VPS server.
My apologies I miss read your suggestion.I am confused. I was recommending if your dev team would be interested in using the VNC protocol so that nothing will have to go through any server after the two clients are connected to each other. This way it reduces the load to the server by 100% and eliminates the additional propagation delay of all inputs and screen changes having to first go through a server before reaching the other client.
We bought the sources knowing beforehand what this system had to offer and how it was structured.
I make suggestions all the time to various companies because when I like a product, I sometimes feel a tweak or two would just make it that much better.
I guess I did. Sorry.It seems you misunderstood my posts.
Trust me, being a developer and seeing people always expecting things for free, I'm usually the "sucker" that donates to everyone if I use a free product on a regular basis.I just think that they delivered what was promised and that we can't really ask them to continue adding features, without being compensated, at least for new features that we might very well be able to add ourselves.
Well, then I think we are very much alikeI'm the one who donates to Wikipedia, Mozilla, etc. because I use their products and I actually feel a little guilty if I don't donate
Sfsameer, if you do implement it, that would be awesome and I would be first in line to pay the v2 upgrade cost...consider VNC implementation done, we will implement it in the next update as soon as we study and figure the technology behind it
Reference : https://bit.ly/2PfPSHjVNC Server captures the desktop of the computer in real-time and sends it to VNC Viewer for display. VNC Viewer gathers your input (mouse, keyboard, or touch) and sends it for VNC Server to inject and actually achieve remote control.
So :The host and client of VNC can talk to each other directly without needing a server (or database) if the IP address and port number of the client are known.
The only time a server (for example running the UltrVNC repeater) is needed with VNC, is to connect a host and a client if the client or host are behind a firewall. In that case, a repeater is needed to make the connection as a proxy between the two IP's and ports of each app. So when a repeater is used, data packets simply flow in one port and get sent out another port. Again, no database transcoding is required.
And as you mentioned, there is a "heavy load" on the database to handle the inputs using the method you are currently using.
My suggestion to use VNC is two fold:
1) By eliminating the database processing, it will lower the server demand and decrease propagation in communication between apps for quicker screen updates, FPS, etc.
2) Also, by eliminating the requirement of a middleman database, it would even allow a client to directly connect to a host using a "reverse connection", eliminating the need for a server or repeater at all.
But this is just a suggestion. Ultimately, I need to be able to remote control (support) both iOS and Android users. So, if your method supports both platforms and VNC protocol can not support iOS, then that would be a deal-breaker for me with the VNC and a major plus for your current method.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?