Message timeouts?

Does beepcore-c handle the issue of message timeouts, ie: if a client 
receiving regular messages has stopped responding or if a sloppily 
written client never responds?

I can't find any discussion of it other than a message by Helen Ryan 
back in January which didn't seem to get a response

"
>What if the server just doesn't reply, e.g. due to programming error, etc?
>  This would also cause beepng to hang forever.  Where the client is part of a
>  larger system or long-running program, this can be a problem.  Should there
>  not be some kind of timeout?  Is this intentional in the BEEP protocol or
>  just an implementation issue?
"
-- 

Andy Dent BSc  MACS  AACM   http://www.oofile.com.au/
OOFILE - Database, Reports, Graphs, GUI for c++ on Mac, Unix & Windows
PP2MFC - PowerPlant->MFC portability


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf