W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

[Bug 14086] New: When performing AJAX type queries, they are already asynchronous and already occur in another thread. However, I have found that parsing the XML reply and converting that to a representation usable by the javascript application can result in freezes to t

From: <bugzilla@jessica.w3.org>
Date: Thu, 08 Sep 2011 14:41:50 +0000
To: public-webapps@w3.org
Message-ID: <bug-14086-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14086

           Summary: When performing AJAX type queries, they are already
                    asynchronous and already occur in another thread.
                    However, I have found that parsing the XML reply and
                    converting that to a representation usable by the
                    javascript application can result in freezes to t
           Product: WebAppsWG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Web Workers (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Specification: http://www.w3.org/TR/2011/WD-workers-20110901/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
When performing AJAX type queries, they are already asynchronous and already
occur in another thread.  However, I have found that parsing the XML reply and
converting that to a representation usable by the javascript application can
result in freezes to the GUI for large amounts of data.  When I tried to put
the processing of the AJAX reply in a web worker (I tried to put the XML
processing and marshaling to javascript amenable format in a web worker), I
found that the web worker could not use the DOM Parser and the javascript data
assembled by the web worker had to be converted to a string to be pushed back
via a message to the main thread.  So web workers do not appear to solve what
appears to be a fairly common problem - a delay processing alot of XML data
from the server.  The ability to assemble data in a handy format in one thread
and then give it to the main thread, without incurring a time penalty to
essentially recreate the data in the main thread, would be nice to have.  It
appears what we have now are multiple processes rather than threads (no data
sharing).  Why not modify the core javascript language to add threads?    (Like
C++0x or Java).  Why can't the web workers use an XML parser?

Posted from: 199.89.158.132
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20100101
Firefox/6.0.2

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 8 September 2011 14:41:57 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT