Reusable Server Kernel

Problem 40 (Note): call to ThreadDelete inside an RSK service?

=============== 2000-09-18 13:08:04 (-04.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
Yeah, that's what I thought, too, Brian. Just wanted to check with you though. Thanks.
=============== 2000-09-18 09:25:14 (-04.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
Hi Dave - I have not thought about this very much.  Each line driver expects that a
service thread will return to its caller when the service thread is done with the 
client.  Each line driver keeps counters, control blocks, etc. that describe the
existence of the service thread and which also manage the state of the connection
to the client.  For example, if a TCP service thread were to delete itself instead of
returning, the client connection would never close.  Messages would pile up on
the service queue, too.  A service thread deleting itself is probably not a good thing
to do.  BKW  
=============== 2000-09-15 12:42:45 (-04.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
What bad things can happen if ThreadDelete is called inside an RSK service to delete itself?