Stack: 1. Windows 7, server and client, client talking to server as localhost 2. qooxdoo dsktop 5.0.1 just now downloaded 3. Chrome browser just updated 4. AllegroServe (Lisp) server
Problem synopsis: remote table load request (and everything else) works for 98% of (it so happens) students. On three we get a puzzle: 1. all events are logged, and the only thing the log shows for these three cases is a changestate from configured to queued; but... 2. the request is in fact received by the server and successfully process and returned with a 200 status; but... 3. the page is hung and cannot even be interrupted. I have to use the task manager to kill it, easily identified as the one using 25% CPU 4. I dummied the data to hardcoded strings and digits and that appears for all other students. Note that for the 98% of working cases the logging shows state proceeding as expected from queued to sending to receiving. My thinking (confirmed by dummy data not helping) is that qooxdoo is already broken when this sequence begins, such that a request gets successfully and correctly sent without qooxdoo logging the corresponding events. Thus my suspect is the preceding loadrowcount request, which might have left qooxdoo in a broken state. I will continue tinkering with the three failing cases to see how they differ, stare at the loadrowcount request, and later start hacking qooxdoo internals. Any thoughts are welcome! Thanks, Kenneth -- Kenneth Tilton 54 Isle of Venice Dr Fort Lauderdale, FL 33301 k...@tiltontec.com http://tiltontec.com @tiltonsalgebra 646-269-1077 "In a class by itself." *-Macworld*
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
