Jason Hudgins wrote:
This begs the question though, are these list resources really all that useful?
Well, I think even though you haven't found a usefulness for those URLs
yet, doesn't mean that they may not be useful in the future.
Using a more "natural" organization for your data will lead itself to
finding various and interesting applications in the future. You are
"future proofing" your URL space.
As well, as I just mentioned in my other reply, it helps to scale the
application a bit more "traditionally" should you ever need to.
As a practical example, maybe your service gets really popular with
folks in Germany. So, you are getting a ton of hits to the
../jobs/de/{language}/ urls.
Maybe you decide that because these clients are on average physically
located in Germany, you buy a hosting service with a point of presence
in Germany, and then want to start serving these requests from that url.
Now, you configure your reverse proxy sitting in front of your
application to issue a redirect to the server that is actually proximal
to their location. They get redirected to:
http://de.incantations.net/.../jobs/de/{language}
Anyway, the point is, you don't want to corrupt your URL namespace if
you can help it.
Adam
