title: RoboSpice and TCP Connection
body: <p>I'm not sure if I should post this here or on github, but I got a weird ticket raised by a client saying :</p>
  
  <blockquote>
    <p>One of the problem we see, that might be the root cause of the API
    dying is that the API replies to the App with the data and HTTP 200 OK
    and closes the TCP session.</p>
    
    <p>However the app does not acknowledge the closing of the session and
    continues trying to use the same old TCP session that is in close wait
    state on the server.</p>
  </blockquote>
  
  <p>Now I'm not an HTTP stack expert nor have time to dig in the Robospice code, so my question is : Is it a client side or a server side issue ? If it's client side, is it a Robospice issue, or a "code12, dumb programmer at work" issue.</p>
  
  <p>The API is written in Python (Flask) and runs along an OpenStack infrastructure.</p>
  
  <p>My project currently use : </p>
  
  <pre><code>Android 4.+
  compile 'com.octo.android.robospice:robospice-retrofit:1.4.14'
  </code></pre>
  
  <p>Thanks for any suggestions !</p>