Timeline for Is making 2 sequential request to server for every webpage better than implementing server to make subqueries with every request?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 4, 2022 at 4:20 | comment | added | Qi luo | edit: actually i guess staleness would only be so if i treat session as a cache rather than updating with every request. | |
| Mar 4, 2022 at 4:07 | comment | added | Qi luo | ... for cookies, then it would mean a new cookie will be made for every profile visited. for server session variable, then there could be a longer duration chance for stale match between username-userid reference if user changes it. it also adds another step to ask client be redirected. may I ask how does http request body help ? thank you for the opinion tho , lol made me tinker a bit more. | |
| Mar 4, 2022 at 4:05 | comment | added | Qi luo | You make a very good point with the consistency and targeting between userid and username on the one URL. I think I would prioritize userid in my case. The reason i choose url is that if user hard refreshes, the url will remain as the truth, and for most cases it is fresh and it wont alter - and even if it does, the inconsistency can auto replace based on fetched data from id param (if exists), if it fails or doesn't exists then on username, otherwise is a 404 link. ... | |
| Mar 4, 2022 at 2:44 | history | answered | Fat P | CC BY-SA 4.0 |