At 8:10 AM -0700 2/17/06, Joseph J. Strout wrote:
At 12:45 PM +0100 2/17/06, Thomas Tempelmann wrote:
> http://www.realsoftware.com/feedback/viewreport.php?reportid=jycozgss
http://www.realsoftware.com/feedback/viewreport.php?reportid=hzqyvxaw
I believe I've filed a similar one as well.
The bug appears to be in the socket event handling code: It allows new
incoming socket events to be processed immediately instead of putting
them into a queue and handling them only if previous socket events
have been handled.
Only if the new event is Error.
I wonder if Aaron, who would probably be responsible for this, even
agrees that this is a bug?
If you're seeing it with anything but Error, it would be. With
Error, it is not.
Is this interleaved socket Error event a new behavior, or did it
work this way in 5.5.5 also?
Regards,
- Lou Forlini
Software Engineer
System Support Products, Inc.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
