Timeline for Design for client-server synchronisation
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 5, 2017 at 11:45 | history | bounty awarded | CommunityBot | ||
| Nov 29, 2017 at 18:42 | comment | added | JimmyJames | So there's lots of ways to distribute data to the servers. S3 makes more sense to me than a CDN. | |
| Nov 29, 2017 at 16:12 | comment | added | turnip | Right. When I said modify the server, I was envisioning storing the configs as env vars, for example. This type of modification would require a restart, and as such we can't use it. Which is why we went with the S3 approach. Apologies if I am being unclear. | |
| Nov 29, 2017 at 16:00 | comment | added | JimmyJames | I'm confused. I thought we were talking about how to redesign it such that it doesn't need to be modified when you change the config. | |
| Nov 29, 2017 at 9:54 | comment | added | turnip | Our backend is built on Flask. As far as I'm aware, any modification made to the server requires a restart for the changes to be taken into account. That's all the info I can give at the moment. | |
| Nov 28, 2017 at 16:46 | comment | added | JimmyJames | @Petar That's what I was getting at in my initial comments on the question. Is there a reason you aren't modifying the server so that it doesn't use hardcoded values that require redeployment? | |
| Nov 28, 2017 at 16:30 | history | edited | JimmyJames | CC BY-SA 3.0 |
added more detail based on comments
|
| Nov 28, 2017 at 16:25 | comment | added | turnip | Simply put, given our current backend infrastructure we have no way of easily updating these hardcoded values that the backend uses on the fly, without having to redeploy the backend after manually updating it. | |
| Nov 28, 2017 at 16:19 | comment | added | JimmyJames | I'm still unsure about what advantage you get from distributing this data to the servers via CDN. I can see why you want to do that with the clients but you have control over the servers, right? I'll add to my answer. | |
| Nov 28, 2017 at 15:57 | comment | added | turnip | I added diagrams and rephrased my proposed solutions. Please check and let me know if that helps. | |
| Nov 28, 2017 at 15:01 | comment | added | JimmyJames | I'm a little unclear on why you would want to have the server depend on the CDN. Can you elaborate at bit? Would it be possible to add a simple diagram to your question? | |
| Nov 28, 2017 at 12:28 | comment | added | turnip | If we are fetching the resources from a CDN (or some other source) for both the server and the client, how should we handle the case where the client is more up-to-date than the server? | |
| Nov 27, 2017 at 18:03 | history | answered | JimmyJames | CC BY-SA 3.0 |