Hi Izzak!
I'll fix the bug when I get to the office. Regarding encodings and
things, I've thought about that too. No changes to existing methods will
be required, thanks to the open-closed principal being at work here.
Best regards,
Chris
Izaak Branderhorst wrote:
Very cool! I'm still worried about the size of your QxHttpTransport
class; I feel that more of it belongs in the QxHttpTransportQueue
class, or even broken into 3 classes. Otherwise, the behaviour I
wanted is there, which is most important at this stage. I'm worried
though that future additions to the QxHttpTransport class for stuff
like encodings will be cumbersome...
I saw a tiny bug on line #853:
< return this._requestCtor();
return QxHttpTransport._requestCtor();
Izaak
On Sun, 15 Jan 2006 22:22:43 -0500, Chris Ricks
<[EMAIL PROTECTED]> wrote:
Hi all,
I've updated these classes. The following semantics now apply:
1. QxHttpTransport classes no longer have a default queue associated
with them - unqueued objects will simply be executed immediately when
.send() is called.
2. QxHttpTransportQueue now REQUIRES an activeCount argument (first
argument - an integer) upon creation.
3. If a QxHttpTransport object is a member of a queue, it will draw
XMLHttpRequest objects from the global request pool.
4. The global request pool has an upper-bound size of the sum of the
active counts of all QxHttpTransportQueue objects. For example:
* 3 QxHttpTransport queues are created, each with 1 request allowed
to be active at any one time and varying numbers of requests allowed to
be queued at any one time.
* The global XMLHttpRequest pool size upper bound is 3.
The pool is managed by QxHttpTransport. XMLHttpRequest objects are only
created as required (i.e. Setting a pool size of 50 does not result in
50 XMLHttpRequest objects being created straight away).
QxHttpTransport now uses more memory, as it holds copies of the various
properties of XMLHttpRequest to allow requests to be entered back into
the queue as soon as they reach an error state or a normal end state.
As always, feedback and comments (as well as questions) are welcome!
QxHttpTransport is pretty much fully documented (other than the fairly
self-explanitary pool-related methods). QxHttpTransportQueue needs some
documentation though. We'll do this at some stage in the very near
future.
Best regards,
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
