删除JAX-RS Service jersey实现中的多个资源

Question

I am new to restful services and willing to get some ideas from the experts.

The application which will be accessing my service is having a datatable-grid (each row of the grid represents an Employee Object/Entity) where user can delete more than 1 records at a time(based on the number of checkbox selected by the user). In such kind of a delete operating how will be the URL representation and how will the data be send to the service?

My Idea

Since the number of rows deleted by the differs (based on the number of checkbox selected by the user), hence I am opting for the query string and below will be the URL representation using which I can get the data in my service:

/deleteEmployees?id=1,2,3

ie a comma seperated values of the id's which will uniquely identify a record in the table.

Based on my Idea, I have a few questions:

1) The query String mentioned above contains of comma-seperated values (ie Ids). Is it a valid URL where query strings will contain this kind of values?

2) Is there any restrictions in defining the query strings of an URL (like the way I did using csv)?

3) Any other alternative of achieving the same in a better and efficient manner?

PS I am new on this and hence looking for different ideas from the experts and try to understand what is correct and what is not.

Answer 1

A comma separated list of Employee ids is a fine way to do it, but I wouldn't put it in a URL with an action in it, ie. /deleteEmployees?id=1,2,3 . REST is more about identifying resources, rather than actions, in URLs. I would either loop through each one of the employee ids to delete and send an HTTP DELETE request for each

DELETE /employees/1 HTTP/1.1
DELETE /employees/2 HTTP/1.1
DELETE /employees/3 HTTP/1.1

Another alternative is to send one HTTP DELETE request to a URL like /employees , keeping the suggested REST identification of resources and using HTTP methods. You would pass the list of ids in an HTTP header.

DELETE /employees HTTP/1.1
Employees-To-Delete: 1,2,3

Take a look at this answer for character restrictions in URLs.