sure, any existing connections continue to be serviced by the old code, and new connections are picked up by the new code. if you need more elaborate lifecycle

sure, any existing connections continue to be serviced by the old code, and new connections are picked up by the new code. if you need more elaborate lifecycle management of components as they are upgraded, then maybe OSGI could do that. erlang's approach really appeals to me though -- not only does the code get upgraded, but it's in cooperation with its message loop so you don't miss a step, and you also get a callback to migrate your actor state.