summaryrefslogtreecommitdiff
path: root/addons/google_account/controllers/main.py
AgeCommit message (Collapse)Author
2020-04-09[REF] google_calendar: Refactor synchronisationLucas Lefèvre
This commit refactors calendar synchronization between Odoo and Google after the main calendar application refactoring. This refactoring takes advantage of two new features from the Google API: - New way of synchronizing resources efficiently[1] Incremental sync is performed repeatedly and updates Odoo with all the changes that happened ever since the previous sync. Each time, Odoo provides the previous sync token it obtained from Google and stores the new sync token from the response. - Event metadata[2] Ability to set hidden key-value pairs with an event, called extended properties. These extended properties are used to store the related odoo event id and the Odoo owner id (see known limitations) Known limitations ================= - Let A and B be two new users (no tokens available). A creates an event in Odoo and invites B. A is the owner of the event (user_id). Now B authenticates to his Google Calendar account and synchronizes his calendar. We cannot send the event to A's calendar since we don't have any access to his Google Calendar. Hence the event his sent to B's calendar. This leads to data de-synchronisation: The owner is A in Odoo but B in Google. The "real" owner (user A) is stored in the Google event's metadata to be able to reconcile the owner for following synchronizations. - Let A and B be two users of Odoo and Google Calendar. And let the Google Calendar of B be private (e.g. if A creates an event in Google Calendar and invites B, B won't see the event in his calendar). If A creates an event in Odoo and invites B. The event is synced to Google Calendar of A. Now B can see the event in Odoo but he can't see it in his Google Calendar. Task 2126717 PR #42031 PR Enterprise odoo/enterprise#8006 [1] https://developers.google.com/calendar/v3/sync [2] https://developers.google.com/calendar/extended-properties
2016-04-27[REF] google_account : code cleaningJérome Maes
- remove unused helpers - add command in case of deeper refactoring one day ... - better variable naming - use contants for Google services urls - add docstrings
2016-04-27[MIG] google_account: migrate into new APIDeep Bundela
2015-09-28[IMP] replace simplejson with stdlib jsonLeonardo Rochael Almeida
The stdlib version of the json library is more recent than the 3.5.3 version we are pinning in `requirements.txt` There is no reason to use it. Closes #6940
2014-07-06[MERGE] new v8 api by rcoRaphael Collet
A squashed merge is required as the conversion of the apiculture branch from bzr to git was not correctly done. The git history contains irrelevant blobs and commits. This branch brings a lot of changes and fixes, too many to list exhaustively. - New orm api, objects are now used instead of ids - Environements to encapsulates cr uid context while maintaining backward compatibility - Field compute attribute is a new object oriented way to define function fields - Shared browse record cache - New onchange protocol - Optional copy flag on fields - Documentation update - Dead code cleanup - Lots of fixes
2014-01-13[REF] Refactoring according to CHS and AL reviewjke-openerp
bzr revid: jke@openerp.com-20140113174157-ins4vf57g0p6v82u
2013-12-19[IMP] Redo tuto to get api key, because Google have changed console UI ↵jke-openerp
during the dev bzr revid: jke@openerp.com-20131219174536-msjd005fxhxgl9qq
2013-12-19[TYPO] Rename google_base_account into google_accountjke-openerp
bzr revid: jke@openerp.com-20131219142514-8epaqnt0mb16xd4n