Given my recent problems with sockets suddenly becoming invalid on the
windows install of webkit, I've decided that I have to modify the code
within ThreadedAppServer.
I think that I have made the proper changes, but I was hoping that
someone (possibly with more webkit experience) could point out any
potential gotchas with my change.

In ThreadedAppServer.py (~ line 150) there is this bit of code;
if sock.getsockname()[1] == self.monitorPort:

I am going to be replacing that with the following;
theSocketName = ''
try:
        theSocketName = sock.getsockname()[1]
except Exception, e:
        print str(e)
        print str(sock)
        continue  <-- is this the correct action to take?
                                
if theSocketName == self.monitorPort:

So it seems to me that if I get an error on any of the sockets, the
defective socket will be ignored in the current pass and hopefully not
picked up during the next pass. 

Can anyone see any problems with simply ignoring the defective socket?

Does this mean that a given user request might be lost?

David London




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to