aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zameer Manji (JIRA)" <>
Subject [jira] [Created] (AURORA-1757) Support ETags in Aurora API
Date Tue, 30 Aug 2016 01:04:20 GMT
Zameer Manji created AURORA-1757:

             Summary: Support ETags in Aurora API
                 Key: AURORA-1757
             Project: Aurora
          Issue Type: Task
            Reporter: Zameer Manji
            Assignee: Zameer Manji
            Priority: Minor

The Aurora API is over HTTP and I think a useful feature of HTTP to support is ETags.

Supporting ETags means that every API response has an ETag header which is a hash that represents
the body. A client can then issue the same API request with the etag value in the If-None-Match
header. If the etag value is identical to what would be produced by the API request, the scheduler
could respond with an empty body and an HTTP 304 (Not Modified).

The benefits of this are clear if clients are polling the scheduler via methods in ReadOnlyScheduler.
Instead of having to deserialize the response, the clients will know for sure the response
is identical and can act appropriately.

This message was sent by Atlassian JIRA

View raw message