On 04/11/2013 09:57 AM, Jeff Mesnil wrote:
>
> I've not addressed the :reload way. I suppose this could be handled
> inside the NotificationRegistration object to re-register the
> notification handlers if a reload occurred. I'll address that in a
> separate issue.
>

The problem is not really the :reload operation itself. It's the actual 
ModelControllerClient API and the underlying connection management which 
don't add up in this case.

As it is now you can restart the server without requiring any action on 
the client. It will try to reconnect once you send the next request. 
Neither re-registering the notification handlers in this case or having 
the client to actively reconnect seems like a good solution to me.

Probably a better way would be to have the client let you create a 
management connection where you can execute requests and register 
notification listeners. At least from an API standpoint it should be 
more clear that you have to open a new connection and re-register the 
listeners yourself. I wanted to do that for a while, maybe now is a good 
time.