News for hackers. Stuff that matters.

A comment on 21 XMPP use-cases and the best ways to achieve them. Parent comment

Re:21 XMPP use-cases and the best ways to achieve them by nyconyco on Monday March 27, 2017 @04:21PM (#13971372)
MongooseIM (and ejabberd) are too big and complex to allow full hot code reloading. Moreover this feature is quite rarely used in any Erlang software.
[ Parent | on HN ]
Re:21 XMPP use-cases and the best ways to achieve them by toast0 on Tuesday March 28, 2017 @02:58PM (#13979544)
I'm not sure how you've measured how often hot code reloading is used? I use it for almost all of my production pushes.

However, I agree that it's generally hard to use it for third party software; upgrades would either become cumbersome because you have to follow the same piecewise upgrade process the developer followed, or the developer would have to do a lot of extra work to ensure upgrades between releases were solid; the recent addition of atomic loading of multiple modules would probably help.

[ Parent | on HN ]
Re:21 XMPP use-cases and the best ways to achieve them by nyconyco on Thursday March 30, 2017 @09:15AM (#13995032)
I could point to this: https://stackoverflow.com/questions/31080970/erlang-hot-code...
[ Parent | on HN ]