The central "model" object (as in MVC) in my app has ten strings properties and one dictionary property. The string properties rarely change (i.e. would be updated only a few times a year). The dictionary property contains three numeric values which could change several times a day, somewhere between twelve times a day (e.g. every hour) to 144 times a day (e.g. every five minutes).
Is it worth separating out the dictionary with its three properties into a separate document and linking this new document type back to the document with the static string properties? This seems appealing as it will reduce the traffic (at least in relative terms) between the remote Couchbase Server and the phone (all changes would originate on the Couchbase Server), but if the objects in my app are subclasses of CBLModel it seems like it would be a headache to "join" the documents together on the phone to create an object with both the static and non-static properties. Not sure if the above is clear... Any advice? -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/d100ac2b-d496-4f1f-a36b-2f9c86f29e76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
