On Thu, May 14, 2009 at 4:26 AM, Jim Hunter <[email protected]>wrote:
> I'm not positive about the request.Rpc, but the remote.Request is not
> reusable, it is a singleton. I would check the Rpc to see if it too is a
> singleton before you spend more time on trying to pool it.
>
Not only is an Rpc object reusable, but reusing them is encouraged. Most
applications need only a single one. Multiple Requests can be outstanding on
a single Rpc object at any one time so there is no reason for multiple Rpc
objects. The whole purpose of the "id" value that is passed to each Rpc
request and returned by the Rpc response is to be able to match a particular
response with its corresponding request.
Of note, though, is that the browsers I've tested (FF3, IE7) strictly
conform to the HTTP standard which says that only *2* HTTP requests can be
outstanding at any one time. This means that if there are two requests
awaiting responses, any additional requests are queued by the browser until
at least one of the outstanding requests completes. I believe that one of
the tabs in RpcExample demonstrates this limit.
Derrell
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
