Ask HN: HTTP Path vs. Query Parameters
What sort of design considerations might sites like YouTube use when deciding between path or query parameters for identifying resources?
For example, YouTube uses a query param 'v' to specify a video id:
youtube.com/watch?v=<video_id>
youtube.com/watch/<video_id>I use the first if video_id can not fit in a hierarchical model
Can you elaborate, I am interested? What do you mean by "if video_id cannot fit in a hierarchical model"?
Like a matrix versus a tree