socket clean-up, crserver exit

A problem that Chromium has had for a while is it doesn't always close 
down cleanly.  When app or crserver process exits, the other processes 
may linger until they're manually killed.

I've checked in some changes to address this.

The network layer had some provision for connection-close callback 
functions but it wasn't fully utilized.  I've updated that code.  The 
connection-close callback that's registered with crNetInit() is now 
called whenever a connection is closed (it was hit or miss before). 
I've updated the Pack SPU to use this properly and will update some 
other SPUs soon.

The other new thing is a crserver config option called 
'exit_if_no_clients'.  It's enabled by default.  Basically, when the 
crserver detects that there are no longer any client connections, the 
crserver exits.  If you'd prefer the crserver to stay alive, waiting 
for future client connections, set exit_if_no_clients=0.

Hopefully I haven't broke anything.  Let me know if I did.

-Brian


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642