Disable Ajax caching, just in case
Reported by Rusty Klophaus | April 15th, 2010 @ 10:33 AM | in 2.0.1
Quoth Mike, on the NewsGroup:
I was experiencing some oddness (dead button clicks), but I'm
not 100%
sure if caching was involved in the problem, for type "text"
ajax
defaults to caching all responses - so I made the addition of
cache: false,
on lines 177 and 213 to disable caching of the response coming
back
from the server. The problem I was having "dead clicks" seemed
to
have resolved.
Is it possible that the state and everything would be the same
and not
cause a message to be sent due to caching? Either way, I'd
rather
explicitly control caching than rely on a default.
Mike
Comments and changes to this ticket
-
Rusty Klophaus April 15th, 2010 @ 10:35 AM
- Assigned user cleared.
-
Rusty Klophaus June 14th, 2010 @ 03:37 PM
- State changed from “new” to “resolved”
(from [d04137392906a0e0cf8dca56de3bb212cba194c6]) Disable caching in nitrogen.js. [#45 state:resolved] http://github.com/rklophaus/nitrogen/commit/d04137392906a0e0cf8dca5...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Nitrogen Web Framework for Erlang
People watching this ticket
Rusty Klophaus
Referenced by
-
45
Disable Ajax caching, just in case
(from [d04137392906a0e0cf8dca56de3bb212cba194c6])
Disable...