finding new contacts and deleted contacts should be same. Just switch userA and B new contacts on userB will be actually deleted contacts in userA. You can even use same code for finding new contacts and deleted contacts.
On Dec 30, 12:23 am, Tb <tho...@bertranfamily.com> wrote: > I'm writing an app to keep contacts on my multiple Gmail/Google Apps > users in sync with a central repository. > In order to perform my incremental updates, I need a way to tie a > contact on us...@gmail.com (assuming this is my active repository) to > that same contact on us...@gmail.com (assuming this one is passive, no > addition/update/deletions performed manually). > > - NEW contacts added on userA are not a problem. > > - For contacts UPDATED on userA, I succeeded by adding an > ExternalProperty on userA that held the value of ContactEntry.getId() > of userB. That way, anytime I picked up an change on a contact of > userA, I'd go and find that same contact on userB and reflect that > change. > > - Then comes the DELETED contacts... Per Google documentation: > "Deleted contacts are shown as entries that contain nothing but an > <atom:id> element and a <gd:deleted> element." Meaning, I lost my > ExternalProperty entry and, with it, the path to find that contact on > userB. > > The obvious solution would be to keep track of my contact links (Ids > of both UserA and userB) in a table on the DataStore. If possible, I'd > like to avoid it... > > Any suggestion? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
