ctfscoreboard icon indicating copy to clipboard operation
ctfscoreboard copied to clipboard

Utilitize HTTP caching for API resources

Open k9delight opened this issue 9 years ago • 0 comments

We should be able to use HTTP Etags for API resources to reduce bandwidth.

Taking an etag from the client and comparing memcache.get(resource_type_md5) gives us the ability to quickly identify if the data has changed, and if to return the new results, alternatively send a 304 not modified if unchanged.

Benefits: bandwidth saved, maybe reduced CPU time?

Costs: more code paths added to the application

No clear consensus if this is worthwhile implementing vs adding other functionality.

k9delight avatar Jun 09 '16 17:06 k9delight