Very nice and it will definitely help newcomers.
A note though about cache in jsonp mode: if you use the automatic
fetching of a callback name on the secondary question mark, the name being
generated, browsers will never ever cache (how could they? The content is
actually different)... and since
Hi Dave -
This so much for pulling this together, it's very useful.
I see some definite gaps that can be closed, when looking at this (for
script/json/jsonp):
- beforeSend/ajaxSend
- dataFilter
- processData
- timeout
Now, error and ajaxError could be handled - but to a limited degree.
If
I created some tickets for the missing features:
http://dev.jquery.com/ticket/5500
http://dev.jquery.com/ticket/5501
http://dev.jquery.com/ticket/5502
--John
On Thu, Nov 12, 2009 at 9:58 AM, John Resig jere...@gmail.com wrote:
Hi Dave -
This so much for pulling this together, it's very
Regarding the abort possibility for jsonp (#5500 = #3442), this brings us
back to the idea of returning an abstraction on top of the actual xhr/script
hack/whatever.
I was curious as to why the whole ajax typology wasn't implemented with a
factory pattern: you would call something like
Oh yes, also, ajax could handle image preloading too imo.
2009/11/12 Julian Aubourg aubourg.jul...@gmail.com
Regarding the abort possibility for jsonp (#5500 = #3442), this brings us
back to the idea of returning an abstraction on top of the actual xhr/script
hack/whatever.
I was curious as
Regarding the abort possibility for jsonp (#5500 = #3442), this brings us
back to the idea of returning an abstraction on top of the actual xhr/script
hack/whatever.
I was curious as to why the whole ajax typology wasn't implemented with a
factory pattern: you would call something like
Re: http://groups.google.com/group/jquery-dev/msg/70b913e489c9fc8f
Here is what I came up with. I built this mostly by looking at the
source to ajax.js so let me know if there is anything that looks
wrong:
http://spreadsheets.google.com/ccc?key=0Aj5JJFjq9rZDdC1OQjJOcmtjTmtBUVdXV2NPczE2R2chl=en
