Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

145
Visualizações
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 à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda