I still haven't remembered what is weird about socketTimeout.
Perhaps you don't get it if you get socketClose or socketError.
(When debugging TCP, I use handlers for all.)
Is your socketTimeout handler in the right path? (An example
situation is when your socketTimeout handler is in the card script
but the actual read is in a handler in the stack script.)
Dar Scott
On Oct 8, 2010, at 12:33 PM, Len Morgan wrote:
Not according to the documentation. And I didn't start off using
the "with message" form. In fact, I never did get around to even
trying that once I discovered that <I> was the one that was making
the mistake (i.e., trying to read more bytes than were there).
len morgan
On 10/8/2010 1:29 PM, Dar Scott wrote:
On Oct 8, 2010, at 12:02 PM, Len Morgan wrote:
It still bothers me though that I never got the socketTimeout
message even though that's exactly what was happening.
I have a vague memory of strange things with this.
I wonder if you don't get the message if you don't use 'with
message' in the read. Maybe that info is just in the result.
Dar
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
