I modified my copy of DatePicker.java and DatePicker.html to reference
resources (images, javascript, and css) from the web server directly
and everything works great now. Hopefully I can throw it out when 1.2
is released. It appears that IE / https / wicket combination causes
some threads to get stuck when lots of images are requested
simultaneously. Has anyone else experienced this?
On 2006-01-27 12:57:11 -0700, Martijn Dashorst
<[EMAIL PROTECTED]> said:
Can you see the requests stalling in the server logs?
As for 1.2: the resource requests will not pass a blocking section. This is
hard to achieve in Wicket 1.1, which is one of the reasons we (mainly Eelco=
)
replaced the internal request processing in Wicket 1.2
Martijn
-------------------------------------------------------
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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
