WinMx Version Differences 3.11

[GhostShip]

WinMX v3.11 Beta Test


Changes in v3.11 Beta 1

- corrected major bug that caused crashes when # of total uploads (dead or running) + download connections + OpenNap servers + channel connections >= 1024
- major re-write of all bandwidth throttle code, old version was allowing outgoing UDP packets to violate bandwidth throttle, which then causes other problems for users with primary connections,
especially ADSL users with limited outgoing bandwidth
- major re-write of channel redirect code, however it hasn't been tested under real-world conditions yet
- bandwidth graph paint code has been greatly streamlined, was taking too much CPU time
- dangerous filetype warning suppress should work now
- bandwidth throttle now has adjustable resolution (and defaults to 200ms instead of 100ms in v3.1 )
- master window second row buttons will now always show in appropriate mode, even if channels and searches are undocked
- secondary connection can be cycled without losing channel connections (click the "Make Secondary Connection" radio button, and your current connection will be disconnected and WinMX will find a new one.)
- several other minor bug fixes

This beta version will be on the same network as the old version 3.1, so search results should still be plentiful.


Notes

Our main objective during this round of beta testing is to improve client stability and improve WPN primary connection efficiency.
We have logged thousands of great ideas and changes that were sent in from our users, but for now we are focused exclusively on making the client
relatively crash-free and able to maintain a very stable network connection. Once this objective has been accomplished, we will release a new final version 3.2, at which time we will begin implementing some new features and refinements.

[GhostShip]

WinMX v3.11 Beta Test

Changes in WinMX v3.11 Beta 2

- corrected major bug that caused crashes when # of total uploads (dead or running) + download connections + OpenNap servers + channel connections >= 1024
- major re-write of all bandwidth throttle code, old version was allowing outgoing UDP packets to violate bandwidth throttle, which then causes other problems for users with primary connections, especially ADSL users with limited outgoing bandwidth
- major re-write of channel redirect code, however it hasn't been tested under real-world conditions yet
- bandwidth graph paint code has been greatly streamlined, was taking too much CPU time
- dangerous filetype warning suppress should work now
- bandwidth throttle now has adjustable resolution (and defaults to 200ms instead of 100ms in v3.1 ) <<
- master window second row buttons will now always show in appropriate mode, even if channels and searches are undocked
- secondary connection can be cycled without losing channel connections (click the "Make Secondary Connection" radio button, and your current connection will be disconnected and WinMX will find a new one.)
- secondary connection message scheduling, so simultaneous searches don't drown each other out
- secondary search stop command, eliminating wasted bandwidth when a search is halted prematurely
- channel flood algorithm now includes /action /emote /me messages
- default channel user limit now 40 instead of 10
- several other minor bug fixes


Notes:
Remember, this beta test version of WinMX is intended for EXPERT USERS ONLY. As with any version of WinMX, you USE IT AT YOUR OWN RISK. If you are uncomfortable with this, do not participate in the beta test.

Very Important: Due to certain protocol changes, BETA 2 connects to it's own network, separate from ALL other versions of WinMX, including BETA 1. Therefore, the amount of search results and other users will be very small compared to other versions. If you are uncomfortable with this, please refrain from downloading BETA 2, as we will be releasing a final v3.2 very, very soon. Also, due to the very small initial size of the network, you may experience some delay connecting. Please just let it run and be patient.

[White Stripes]

does (did) 3.11 beta 2 use the network we know today as its 'own network' or did it really have some serious changes? were they good/bad/indifferent?

[GhostShip]

It was quite common for a beta to have subtle changes that ensured the main network was never disrupted, one of the most common would have been the utilisation of a different port at the caches to ensure that there was no cross pollination of network users, this ensured that if a protocol change went wrong it would only affect those running the test version.

Older versions used different packet numbers for some important network functions, once again this would have ensured insulation of  the two sets of users, as to whether the changes where better I think we can say they usually where as the current main network protocol has some useful but not initially obvious tricks and methods inbuilt into it to assist in creating a scalable network that employs measures to acheive self stabilisation when the network is first forming,t hese have obviously evolved over time in response to observed failures.