A
Ahdriano
Guest
Hi,
I have a program that runs on multiple machines on a service network (the program also has a GUI that is always open on the computer). This service queries a server API for execution information and returns the status of the executions. It turns out that this is generating a significant amount of requests and would like to create a centralizer, ie on a local network computers would talk to a computer on the delegated network as a centralizer and this centralizer would talk to the server.
I thought of opening a socket server thread in the delegate computer service as a centralizer, but I don't know if this is the best solution. Has anyone needed to do something similar or have any suggestions?
Thanks in advance.
Continue reading...
I have a program that runs on multiple machines on a service network (the program also has a GUI that is always open on the computer). This service queries a server API for execution information and returns the status of the executions. It turns out that this is generating a significant amount of requests and would like to create a centralizer, ie on a local network computers would talk to a computer on the delegated network as a centralizer and this centralizer would talk to the server.
I thought of opening a socket server thread in the delegate computer service as a centralizer, but I don't know if this is the best solution. Has anyone needed to do something similar or have any suggestions?
Thanks in advance.
Continue reading...
