I guess it will get an exception and stop itself . right?
So the app should make some space and restart the replication.
Here come an architecture question:
Let say the device(app) should be able to work offline aswell and hold as many docs as possible.
What will be the proper way to sync a a large number of docs to a limited space devices?
Is that should be all in the hand of the sync server? Controlling the docs for a specific device? Making the sync gateway device aware?
Or does the device should take a roll in this game :
Let say the app can detect when it rich to a certain threshold and then stop the replication.
Now …it should make some space by removing old docs from its local db - How to do it without remove it from the server db?
Then the app should inform the server it has some additional space and want some additional docs… and start the replication?