Etag computation in i18n #464

Closed
cescoffier opened this Issue Apr 3, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@cescoffier
Member

cescoffier commented Apr 3, 2015

The idea is quite simple. The i18n service should compute and maintain an ETAG per locale of the current messages. The ETAG can be computed by using a hash algorithm on the current set of messages (md5 or sha1 should be enough) by tracking the last modification for a given locale. Every time messages changes, the impacted ETAGS are computed.

By doing this, the controllers providing the messages can use the computed ETAG and so benefit from client cache features.

@cescoffier cescoffier added this to the 0.8.1 milestone Apr 3, 2015

@cescoffier cescoffier added the planned label Apr 3, 2015

@cescoffier

This comment has been minimized.

Show comment
Hide comment
@cescoffier

cescoffier Apr 6, 2015

Member

Here is the list of actions:

  • - ETAG computation
  • - Store computed ETAG per locale
  • - Update ETAG on change events
  • - Update the controller to insert the computed ETAG in the response
  • - Check in integration tests that the ETAG are set correctly
Member

cescoffier commented Apr 6, 2015

Here is the list of actions:

  • - ETAG computation
  • - Store computed ETAG per locale
  • - Update ETAG on change events
  • - Update the controller to insert the computed ETAG in the response
  • - Check in integration tests that the ETAG are set correctly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment