I don’t think that all these messaging systems are meant for realtime applications.
I didn’t either, but when we see average case scenarios of 4ms overhead with strict tech like RabbitMQ it makes us wonder what something like NATS could cut that down to.
The client uses the same technique as the server: a separate thread for transmission and serialization.
Chat is a more complex problem and a good example of why Quasar is so important. Chat is not actually separate. There are tentacles from the monolith that are still attached which result in the issues that are present. We are definitely targeting those.
The only Erlang we employ is ejabberd itself and mods made to it.
The Activity Tracker was the first player facing feature to use Quasar in it’s infancy (before we really knew it would be what it is today).
There are a lot of things we want to change around that behavior to use the more mature aspects of Quasar, because they simply didn’t exist at that time.
Sequencing and quality of service are definitely considered in the grand scheme of things. This is why simulation frame data will be an interesting exploration. 
All of ESI has been in Kube from the beginning. I think we adopted Kube just as it hit 1.0. Then each of the features mentioned in the blog post have had some aspect in Kube as well.
could be British
BRB changing dev name.
Unfortunately you will need to download and install the launcher again.
https://binaries.eveonline.com/EveLauncher-1549135.276.24.exe
This doesn’t require you to download any eve client files again.
The beta tier has been rolled back to 1548102, so it should be safe again. Still investigating the plan to unlock updating for those on 1549039
If you have version 1549039 you will not be able to switch back to the release branch.
We are still investigating a work around.
Seems it really wants to stay in beta mode. Sorry about that.
The work around to that is to force it back to release mode.
First uninstall to make sure you don’t have the beta launcher.
Then with regedit navigate to Computer\HKEY_CURRENT_USER\Software\CCP\EVE and change the key “LauncherType” to 0
Then install the latest launcher from the site and you should be in release mode.
Heya,
The beta launcher might have exaggerated the existing “Oops I forgot all the accounts because there are three thousand launchers running in the background” issue that most people fix by either nuking the processes or changing the release tier. I’m not really sure what the connection is between them yet.
However, 1516567 should alleviate an issue I think may be related to this. Seems we had some rogue threads that refused to biomass themselves.
They have been given cyanide capsules with ten second dispersal timers. So hopefully the extra running launcher will, in a worst case scenario, die off within ten seconds.
I’ve only gathered this info from a few bug reports and forum threads. If you have any other patterns that might make sense, please add a comment here.
Will keep an eye on this and see if it is sane enough to promote to release next week.
Thanks!
devtrackers.gg
