Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

136
Vistas
Cache discriminator viable approach in web pages

In the project i have developed till now, i usually add a random number to each request of data or file related to the project. I have to specify that the projects i am talking about are web application, and cache discriminator is not applied to third party library (eg : angular) but only to my js files and ajax calls.

The idea work fine but i wonder why i can't ask to the servere which is it's version, and use this number as cache discriminator (instead of a random number that will change on each request). I would like to proceed in that way only for the "file discriminator" and not for ajax call discriminator (ajax request should never be cached, file request can be cached if the application does not change).

In that way my custom javascript files can be cached by browser and be valid until i publish a new version. Now i don't know if it's a lack of my knolwedge or what, but i never heard about that tecnique, and i would like to know if there are some loophole i am not seeing (and that's may be why no one adopted this approach).

about 4 years ago · Juan Pablo Isaza
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda