You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a newbie on rust and proxy stuff, so any help is appreciated!
I have a setup where multiple servers (around 10) are connecting to a single client. Each server and client has its own configuration file. The setup looks like this:
For each server, I have separate configuration files that differ only by the service name (e.g., services.a, services.b):
Is there a more efficient or elegant way to manage this setup? Right now, I have to maintain 10 separate files for server and client sides, which feels redundant.
What would be a better approach to handling connection checks? Currently, I am polling each server until a connection is established. However, the connections are not persistent—they might be lost after some time (e.g., a day), and the server will attempt to reconnect later, which could happen as infrequently as once a day or even less. Polling every 10 seconds is problematic for some operations, but decreasing the interval to 1 second seems wasteful. Is there a more efficient way to manage this, or should I stick with frequent polling? How detrimental is this approach in practice?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm a newbie on rust and proxy stuff, so any help is appreciated!
I have a setup where multiple servers (around 10) are connecting to a single client. Each server and client has its own configuration file. The setup looks like this:
For each server, I have separate configuration files that differ only by the service name (e.g., services.a, services.b):
Client configuration, the files differs by 'remote_addr' and 'client.services.a':
I have two main questions:
Is there a more efficient or elegant way to manage this setup? Right now, I have to maintain 10 separate files for server and client sides, which feels redundant.
What would be a better approach to handling connection checks? Currently, I am polling each server until a connection is established. However, the connections are not persistent—they might be lost after some time (e.g., a day), and the server will attempt to reconnect later, which could happen as infrequently as once a day or even less. Polling every 10 seconds is problematic for some operations, but decreasing the interval to 1 second seems wasteful. Is there a more efficient way to manage this, or should I stick with frequent polling? How detrimental is this approach in practice?
Beta Was this translation helpful? Give feedback.
All reactions