何时使用@QueryParam vs @PathParam(When to use @QueryParam vs @PathParam)

 我没有问过这个问题： @PathParam和@QueryParam有什么区别？ 
 
 这是一个“最佳做法”或惯例问题。 
 
 什么时候使用@PathParam vs @QueryParam 。 
 
 我可以想到的决定可能是使用这两种来区分信息模式。 让我在下面说明我的LTPO - 不太完美的观察。 
 
 PathParam使用可以保留用于信息类别，这将很好地落入信息树的一个分支。 PathParam可用于深入实体类层次结构。 
 
 而QueryParam可以被保留用于指定属性来定位类的实例。 
 
 例如， 
 
 
 
 /Vehicle/Car?registration=123 
 
 
 /House/Colonial?region=newengland 
 
 
 /category?instance 
 
@GET
@Path("/employee/{dept}")
Patient getEmployee(@PathParam("dept")Long dept, @QueryParam("id")Long id) ;
 
 vs /category/instance 
 
@GET
@Path("/employee/{dept}/{id}")
Patient getEmployee(@PathParam("dept")Long dept, @PathParam("id")Long id) ;
 
 vs ?category+instance 
 
@GET
@Path("/employee")
Patient getEmployee(@QueryParam("dept")Long dept, @QueryParam("id")Long id) ;
 
 我不认为有这样做的标准惯例。 在那儿？ 不过，我想听听人们如何使用PathParam和QueryParam来区分他们的信息，就像上面的例子。 我也很乐意听到这个做法背后的原因。 

I am not asking the question that is already asked here: What is the difference between @PathParam and @QueryParam
 
This is a "best practices" or convention question.
 
When would you use @PathParam vs @QueryParam.
 
What I can think of that the decision might be using the two to differentiate the information pattern. Let me illustrate below my LTPO - less than perfect observation.
 
PathParam use could be reserved for information category, which would fall nicely into a branch of an information tree. PathParam could be used to drill down to entity class hierarchy.
 
Whereas, QueryParam could be reserved for specifying attributes to locate the instance of a class.
 
For example,
 
 
 
/Vehicle/Car?registration=123
 
 
/House/Colonial?region=newengland
 
 
/category?instance
 
@GET
@Path("/employee/{dept}")
Patient getEmployee(@PathParam("dept")Long dept, @QueryParam("id")Long id) ;
 
vs /category/instance
 
@GET
@Path("/employee/{dept}/{id}")
Patient getEmployee(@PathParam("dept")Long dept, @PathParam("id")Long id) ;
 
vs ?category+instance
 
@GET
@Path("/employee")
Patient getEmployee(@QueryParam("dept")Long dept, @QueryParam("id")Long id) ;
 
I don't think there is a standard convention of doing it. Is there? However, I would like to hear of how people use PathParam vs QueryParam to differentiate their information like I exemplified above. I would also love to hear the reason behind the practice.

原文：https://stackoverflow.com/questions/11552248