Timeline for answer to Synchronize multiples REST api, centralized into 1 web application by Adam Wells
Current License: CC BY-SA 4.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2019 at 22:41 | comment | added | Benjamin B. | I think i will have a problem because if i sync the other sources at 00h00, they will have the updatedAt = 00h00, and the next cron will take them, etc, what do you think about that ? | |
| Feb 22, 2019 at 22:37 | vote | accept | Benjamin B. | ||
| Feb 22, 2019 at 22:41 | |||||
| Feb 22, 2019 at 22:35 | comment | added | Benjamin B. | 00h00 => Get contact from source #1 updatedAt >23h55 (found one 23h56)=> Send to the other sources (change updatedAt everywhere to 23h56) 00h05 => Get contact from source #2 updatedAt > 00h00 , etc. | |
| Feb 22, 2019 at 22:29 | comment | added | Adam Wells | I did, yeah. I suppose that i wasn't clear. I meant that for each source to restrict for recrods updated in the last 5 minutes. | |
| Feb 22, 2019 at 22:25 | comment | added | Benjamin B. | Thank you for your response, unfortunately there is no webhooks on 3 sources (it could be possible to add a kind of webhooks on the e-commerce website, but i'll have to spend more time on the project, and that is not possible). So I think i will continue on the workflow i described. Did you see my remark on the second cron execution and the potential problem with the updatedAt column ? | |
| Feb 22, 2019 at 22:01 | history | answered | Adam Wells | CC BY-SA 4.0 |