When the browser loses connection to the server (server down, bad internet for the client, etc), Meteor automatically queues any server method calls (after running the simulation in the browser and optimistically updating the UI) and runs them when the connection is restored. This is a great feature and I loved it since day 1!
My question is - what are the limits of this - for how long will it keep re-trying and queuing the methods?
At some point does it give up and all the minimongo changes from the simulated methods roll back?
Thanks!