Service - Sort Result: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 7: | Line 7: | ||
https://bitbucket.org/stb_vit/sortresult_main/src/master/ | https://bitbucket.org/stb_vit/sortresult_main/src/master/ | ||
= Notes = | |||
* The data stored here should include everything the client request might need to render results to the user, so no additional calls are needed (eg all possible media that might be shown as a thumbnail, and how likely that thumbnail would be shown)(eg pricing info min price/max price/most common sold price/etc) | |||
* Client uses sortResultId to pull results | |||
* ComplexFilter stores unique ids only for a filter, [[Service - Search Result Main]] takes results from ComplexFilter and adds all data client might need. Sort Result Main service copies the data from Search Result Main and structures it for sorted results | |||
[[Category:Backend services| Sort Result Main]] | [[Category:Backend services| Sort Result Main]] |
Revision as of 11:02, 4 November 2020
Overview
Service that handles sorted results that come from the Service - Search Result Main service. Sorted results are stored/cached so subsequent requests do not need to generate the sorted results again.
Repository
https://bitbucket.org/stb_vit/sortresult_main/src/master/
Notes
- The data stored here should include everything the client request might need to render results to the user, so no additional calls are needed (eg all possible media that might be shown as a thumbnail, and how likely that thumbnail would be shown)(eg pricing info min price/max price/most common sold price/etc)
- Client uses sortResultId to pull results
- ComplexFilter stores unique ids only for a filter, Service - Search Result Main takes results from ComplexFilter and adds all data client might need. Sort Result Main service copies the data from Search Result Main and structures it for sorted results