Skip to content

Releases: microup/vbalancer

v0.8.5

09 Jul 19:15
24f808e
Compare
Choose a tag to compare

Implement new proxy logic

  • Revised proxy logic
  • Fixed errors with various preallocations
  • Fixed tests

v0.8.4

14 Aug 06:51
3110350
Compare
Choose a tag to compare

The logic for working with log files has been fixed.

v0.8.3

13 Aug 10:24
5c95f4d
Compare
Choose a tag to compare

Improve logic for connecting to peers.

v0.8.2

11 Aug 10:43
cdf629b
Compare
Choose a tag to compare

Improve core logic

v0.8.1

09 Aug 09:52
6a0d56c
Compare
Choose a tag to compare

Cache support has been added for the blacklist of IP addresses.

v0.8.0

08 Aug 19:51
bc85d02
Compare
Choose a tag to compare

Improve core logic and update new config structure.

v0.7.9

07 Aug 16:58
e0de019
Compare
Choose a tag to compare

Improve the logic of the proxy core.

v0.7.6 Blacklists functionality has been implemented

13 Feb 19:22
d6cfc26
Compare
Choose a tag to compare

Blacklists functionality has been implemented. Now, IP addresses can be added to the configuration file to reject requests, which will also allow for protection against DDOS or unauthorized access by a specific address

v0.7.5 improved configuration support for better proxy performance

11 Feb 09:10
a38b02a
Compare
Choose a tag to compare

In this version, flexible support for configuration settings has been added to the configuration file, which allows for a more precise description of the necessary connection parameters for the client and the peers between which switching occurs. This MR was tested with 7 connected peers and one active client, which in real-time sent 1000 requests, during the tests there were no problems, the configuration settings used in the configuration file are provided in this build. If you need higher parameters, you can try to change the settings of the following keys: clientDeadLineTime, destinationHostDeadLine, connectionSemaphore, and countDialAttemptsToPeer, these keys are located in the config.yaml file. The output of results to the client was also corrected.

v0.7.4 the proxy mechanism has been revised

08 Feb 07:08
33860ed
Compare
Choose a tag to compare

The proxy mechanism has been revised; there was an error in the old code where checking the availability of a peer was done in one connection while another connection was trying to send data at the same time. This has now been fixed and if the proxy cannot connect to a peer within 1 ms, it automatically switches to a new peer. The number of switches is limited to the number of peers specified in the configuration file.