Geek Answers Handbook

REST Temporary Views

Say I have a hypertext-based RESTful service that simulates an ice cream shop. To better manage my store, I want to be able to display the daily number of listings and the dollar value of each ice cream sold.

It seems that this reporting feature can be presented as a resource called DailyReport. DailyReport can be generated quickly, and there seems to be no advantage to actually storing reports on the server. I want only DailyReport for a few days, on other days I do not need to receive DailyReport. In addition, storing DailyReports on a server would make it difficult for customers who need to remember to delete reports that they no longer need.

The daily report is temporary; his presentation can be obtained only once. One way to do this would be to offer the "/ daily-reports", POST link, which will return a response containing the DailyReport view that lists the sales data for that day.

Edit: let it also say that I really want to make a POST request. DailyReport has many different options for creating a view, such as sorting the ice cream types alphabetically, by dollar value - or including hourly breakdowns - or optionally including the temperature for that day - or filtering out certain types of ice cream (as a list). Instead of using request parameters using GET, I would prefer the POST DailyReport view with the appropriate parameters (using a well-defined custom media type to document each option). The view I presented will display my parameters along with the report itself.

Is this the right way to think about a problem or use a different approach? If it is correct, what special considerations may be relevant when implementing the DailyReport resource? (For example, it would probably be impractical to set the Location header when returning after a POST request).

+5
source share
4 answers

If you want to receive daily reports for the past days, you can implement it as a GET before /daily_reports/2009/08/20. I agree with John Millikin that POST is not needed here - there is no need for something like this to be a user-created resource.

The advantage of reporting every available day as your own URI is cacheability.

EDIT: , daily_report/ daily_reports/yyyy/mm/dd .

+4

POST , . :

GET /daily-report/

200 OK
Pragma: no-cache
<daily-report for="2009-04-20" generated-at="2009-4-20T12:13:14Z">
    <!-- contents of the report here -->
</daily-report>

: URL- , REST. RPC, , SOAP. RPC , , , RESTful.

+2

, POST . , . , .

-

POST /DailyReportRequests

, , , .

, , , DailyReports, . OpenSearchDescription - Query.

+2

, . , , /daily-report, , 11:59 , 00:01, A) , , , B) . , .

+1

More articles:


All Articles