Is there a mechanism to prevent a client from automatically connecting to DDP_DEFAULT_CONNECTION_URL ? I have a client application that receives realtime document updates as a new feature. I would very much like to control the connection state from the get-go, yet still use much of the meteor-client-side goodness instead of doing management of the DDP connection and resulting document channel publication.