Jove,

I have seen very familiar behavior in an application I'm building with
Ext.  I poll the server for a JSON response, and every once in a while
I notice that the transport.responseText is empty, and my function
would throw an error.  More details in this ticket:

http://prototype.lighthouseapp.com/projects/8886/tickets/128-string-evaljson-throwing-a-typeerror

I've since refactored to use transport.responseJSON, and the problem
with that part of the application seems to have abated.  However, the
entire application is Ajax, and every so often I will have a response
come up empty.   Do the Ajax internals work the same way for
transport.responseText as for transport.responseJSON?

Also, if you have a patch, I'd love to see it!

Best,
Chris

On Jun 26, 7:01 pm, jove4015 <[EMAIL PROTECTED]> wrote:
> aha - found someone else who seems to have found out why:
>
> http://prototype.lighthouseapp.com/projects/8886-prototype/tickets/18...
>
> On Jun 26, 6:55 pm, jove4015 <[EMAIL PROTECTED]> wrote:
>
> > I wish it were that simple... I just did a quick grep through all of
> > the Ext JS code I include and there's no reference to XMLHttpRequest
> > outside of comments (and certainly no reference to
> > XMLHttpRequest.prototype)... when I check the contents of
> > XMLHttpRequest.prototype in Firebug they match what I see on a page
> > that does not include Ext.
>
> > I'd say maybe it's Firebug but the bug that caused me to find this in
> > the first place happens in IE 6/7 and Safari 2/3 as well... really it
> > might even happen in Opera, I just haven't looked.
>
> > On Jun 26, 6:46 pm, "Frederick Polgardy" <[EMAIL PROTECTED]> wrote:
>
> > > Maybe ExtJS mucks with the XHR prototype in some way?
>
> > > On Thu, Jun 26, 2008 at 5:38 PM, jove4015 <[EMAIL PROTECTED]> wrote:
>
> > > > Yeah, these calls are definitely asynchronous...  So *both* types are
> > > > happening here.
>
> > > --
> > > Science answers questions; philosophy questions answers.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Spinoffs" group.
To post to this group, send email to rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to