Problem in XmlRpcListenerService with Stream Close throwing InvalidOperationException

I looked at the code history and it appears issue 27 (r38 vs. r63) moved Close 
to the finally block. I guess this is for making sure that any exception closes 
it properly (from history). I am unsure of protocol of when an exception occurs 
in your framework but this should be bulletproof. I little ugly but we always 
do a standard close like normal. In the case of error 
(invalidoperationexception, we flush, sleep 10 seconds and then close. we wrap 
the whole thing in try/catch so if it fails, we dont throw unhandled exception.

Original issue reported on code.google.com by ChasC...@gmail.com on 20 Mar 2011 at 11:27

AnantLabs / xmlrpcnet

Problem in XmlRpcListenerService with Stream Close throwing InvalidOperationException #89