Thanks Jen! I will take a look at it. Yeah, I have read the existing books on map and reduce for couchdb but none of them deal with complicated cases. They are quite broad.
I have a few follow up questions regarding this architecture - Q1 Do you happen to have a suggestion on the push notification system I can use for messaging. I was thinking of having a java server which checks the new messages and sends a push notification accordingly. Having a parameter like isPushed in the message structure or something. Is this a recommended approach? Q2 when the user actually opens the app after push notification I assume it would take a few seconds to get these messages. Is there a way to reduce this lag or delay? I know xmpp is pretty fast but it's a whole new implementation. Can we do something to get similar performance? Q3. The other bit is when a message arrives from a new user who's information isn't available on the local DB. There would also be a lag in pulling this user info. Any suggestions for to make this better? At the moment I am packing in the name of the user with every message and also thinking of putting in the photo link to amazon in the messages, so I can show something to the user and then when he clicks to see the user details, I show a loading screen if the user details aren't available while I pull it. -- 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/306ca3eb-c270-43c2-8be9-f8a6c12ac62e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
