Jörn Zaefferer schrieb:
> Hi Stefan!
>> your guess is not even close. If it was about the 'internals' then you
>> would not hear about it because is my job to fix it.
>>
> Ok, sorry.
>> If you take a look in the code you will see
>>
>> jQuery.ajax(
>> {
>> success: function(response)
>> {
>> xml = $.httpData(response);
>> ...
>> }
>> }
>> )
>> I had to use '$.httpData' so I can work with $('nodename', xml). Before
>> version 1.0.1 I never needed to use it. Now in version 1.0.2 the
>> '$.httpData' is useless.
>> Try to imagine how this impacts a real application, with thousands lines
>> of code.
>>
> Oh right, that is really ugly. That was quite a heavy API change.
> According to the revision history, John added the call to $.httpData
> with revision 278, I have no idea why that was necessary...
That was kind of my fault I guess. John and I agreed, after I reported
that to the list, that it's absolutely not intuitive to have the XHR
object instead of the loaded data passed to the success callback.
Besides that it was described in the docs like that anyway.
So there was the decision to fix that according to the docs or change
the docs. I think everybody agrees on that it's much more useful to have
the data in the success callback than the XHR object which would have
meant that everybody had to use the internal $.httpData function to get
the data out.
I think, John pointed that change out quite obvious on the list.
-- Klaus
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
