The path variables can represent hierarchy:
They do that because there are a lot of RPC systems using GET requests to change data in the server (fail!! Get must be a safe method)īut if you use path variables, all of this services can cache your GET requests. Most of the web cache services on the internet don't cache GET request when they contains query parameters. You can use both of them, there's not any strict rule about this subject, but using URI path variables has some advantages: Hope this helps - I appreciate the explanation might be a bit fuzzy :) (I know, arguably, you could say that the &noemail=1 or whatever parameter it is can be used as a path param and generates 2 separate pages - one with the email on it, one without it - but logically that's not the case: it is still the same page with or without certain attributes shown. For instance, if the profile URL supports a parameter which specifies whether to show the user email or not, I would consider that to be a query param. If a parameter passed in the URL is likely to change the page layout/content then I'd use that as a queryparam. Also, another considerent to this is that the page denoted by the URL which includes the path param doesn't change - the user will set up his/her profile, save it, and then unlikely to change that much from there on this means webcrawlers/search engines/browsers/etc can cache this page nicely based on the path. I personally used the approach of "if it makes sense for the user to bookmark a URLwhich includes these parameters then use PathParam".įor instance, if the URL for a user profile includes some profile id parameter, since this can be bookmarked by the user and/or emailed around, I would include that profile id as a path parameter. I would also love to hear the reason behind the practice. Is there? However, I would like to hear of how people use PathParam vs QueryParam to differentiate their information like I exemplified above. I don't think there is a standard convention of doing it. Whereas, QueryParam could be reserved for specifying attributes to locate the instance of a class. PathParam could be used to drill down to entity class hierarchy.
PathParam use could be reserved for information category, which would fall nicely into a branch of an information tree. Let me illustrate below my LTPO - less than perfect observation. When would you use vs I can think of that the decision might be using the two to differentiate the information pattern.
What is the difference between and is a "best practices" or convention question. I am not asking the question that is already asked here:
0 kommentar(er)
