Ask HN: HTTP Path vs. Query Parameters

2 points by lunch ↗ HN
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>
Instead of sticking it in the path:

  youtube.com/watch/<video_id>

3 comments

[ 101 ms ] story [ 66.4 ms ] thread
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"?