-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.8 #150
Comments
I've already started on #125 - I'm only missing the receiving part of it. The reason I want to do it now is a |
Dont change the serialize or use LibCompress which breaks all compatibility. |
I wasn't planning on breaking any compatibility but the |
I dont think all these changes should be in v2.8. Many should be in v3.0, because I don't think RCLootCouncil is very important addon at the end of expansion. Since we're going to restructure RCLootCouncil in v3.0 anyway, it's better to implement some features there instead, for example, Optimize reconnect data #125. This will spend you lots of time to fix it in v2.8, but it should not be a problem in v3.0 |
I have planned to implement pure LUA version of DEFLATE algorithm, which is used by zip. According to my tests, it takes ~200 bytes to transmit all equipped item strings if the data is compressed by zip. However, it will be long time if I manage to make it work and fast. Speed expectation: as fast as libcompress's |
That's why I've mostly chosen those that's almost finished anyway. I'd very much like to get the PL stuff out now while especially many uses PL, to get a feel for how it's received. The rest is just optimizations, a lot of which is easily reuseable in later versions.
While true, it's not the right mindset to have, and is no excuse for not doing any updates (a lot of people still use it). Besides, I'd rather do new features and get feedback now where any potential shortcomings doesn't matter too much, than finding out at the start of the next xpac that feature x breaks everything.
If you think it's worth it, then cool. |
2.8 is released, not all of the bullets made it into the release though. Closing this. |
Mandatory
Included if ready
Nice to have, but might be pushed
The text was updated successfully, but these errors were encountered: