It seems to be an IE wierdness.

With Firefox, when an html page contains N links to exactly the same
resource, Firefox opens one connection and requests this resource once.
When the resource is returned, it is then used in all N places.

With IE, IE immediately opens N concurrent connections to the server and
issues a request for the same resource over each connection. When the
first response is received, IE then abruptly closes all the other
connections. But of course this big burst of socket-creation and
parallel data transfer can bog down networks and servers.

This IE behaviour was causing nasty "broken socket" warning messages
from Tomcat's ExtensionFilter because browsers really shouldn't close
connections; the server should do that after the response is complete.
I've silenced this warning, but AFAIK there isn't anything that can be
done about IE's behaviour except moving to a better browser.

Regards,
Simon

Geetha Rodricks schrieb:
> Hi
>
> Did you get anywhere with this issue - I have found the same issue
> We have a tree2 component with  lots of nodes.
> To render the tree I get to see multiple gets of the same image which is
> definitely slows the rendering of the tree.
>
> Is there any way to avoid that ?
>
> Thanks
>
>
> Michel Goldstein wrote:
>   
>> Hi,
>>
>> I'm trying to track down a problem that seems to affect a few users of our
>> application. We have a fairly large tree to display (about 1500 nodes)
>> using
>> Tomahawk's tree2 component (with client-side toggle). In most cases, it
>> does
>> take some time to load (as it has to load all nodes and each generates a
>> quite large amount of Javascript/html), but in some cases it takes a LONG
>> time to load (think 2 seconds to 2 minutes). When I look at the Tomcat
>> access logs, I see things like:
>>
>> [02/Jul/2007:11:42:49 -0800] "GET
>> /ptd/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11819657/tree2.HtmlTreeRenderer/images/line-
>> trunk.gif HTTP/1.1" 200 466
>> [02/Jul/2007:11:43:00 -0800] "GET
>> /ptd/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11819657/tree2.HtmlTreeRenderer/images/line-
>> trunk.gif HTTP/1.1" 200 466
>> [02/Jul/2007:11:43:00 -0800] "GET
>> /ptd/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11819657/tree2.HtmlTreeRenderer/images/line-
>> trunk.gif HTTP/1.1" 200 466
>> [02/Jul/2007:11:43:00 -0800] "GET
>> /ptd/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11819657/tree2.HtmlTreeRenderer/images/line-
>> trunk.gif HTTP/1.1" 200 466
>> [02/Jul/2007:11:43:00 -0800] "GET
>> /ptd/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11819657/tree2.HtmlTreeRenderer/images/line-
>> trunk.gif HTTP/1.1" 200 466
>> ...
>>
>> on and on. The only common thing among those users that I have seen so far
>> is that they all use Internet Explorer 6 and seem always to have this
>> issue.
>> I tried to run IE6 on my computer with all the configurations they've told
>> they had, and wasn't able to reproduce it. Does anybody know what metadata
>> is sent by the ResourceLoader that could "fool" their IE into thinking
>> that
>> it needs to load this image over and over again?
>>
>> As of versions, I'm using:
>> myfaces/tomahawk: 1.1.5
>> tomcat: 5.5.9
>>
>> Thank you,
>> Michel
>>
>>
>>     
>
>   

Reply via email to