>> 2) Ajax.Response objects
>> Instead, I envision a *single* Ajax.Response object per Ajax.Request,
>> to be updated as many times as necessary while the XHR progresses to
>> completion (readyState value).
>
> I know that every JavaScript implementation is single-threaded,
> but--theoretically--couldn't this lead to race conditions? (Eg. when
> Response instance changes while you're processing it)
>
> But if you spot places where you can reduce processing being done,
> optimization patches are always welcome.

My humble opinion:

I could store the response object elsewhere, and there is no real
reason to forbid me from doing so (I hate when frameworks reuse the
objects they handle to the developer).

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to