Ticket #6138 (closed enhancement: invalid)
Add option to not delete jsonpCallback upon execution
|Reported by:||orensol||Owned by:||orensol|
|Keywords:||jsonp, jsonpcallback, garbage collection, cache||Cc:|
When using jsonpCallback to set a static callback function, there should be the ability to have the function remain in scope and not garbage collected.
If I call the exact same jsonp request twice, the first jsonpCallback execution deletes itself, and then the second fails on being undefined.
Maybe there's also an option to cache the response of the first request, and on subsequent requests return the cached result instead of making the entire request and callback cycle?
- Priority set to undecided
- Type changed from bug to enhancement