How successful and pleasant would it be if I used only BreezeSharp for data management in a Mobile App? With the ability to export/save/import locally, I could imagine a scenario where I pull from the server and then work mostly in the EntityManager cache.
The question of how much the cache holds, and how it deals with overflow come to mind. I also wonder if I would end up writing a lot of code to manage exported entities if the cache doesn't have a disk-based overflow mechanism.
The cache is in-memory only, so it is limited to the amount of memory on your mobile device. That said, this is typically enough for 10's of thousands of entities on even pretty limited devices. Not sure I would go down the route of an overflow mechanism, other than simply detaching entities from the cache, letting the garbage collector clean them, and just go back to the server for any entities not in the cache.