title: Websockets on stellaris board running lwIP 1.3.2
body: <h2>What I'm doing</h2>
  
  <p>I'm implementing a websocket server on a stellaris board as the title says. At the moment I'm able to establish connection to the client and send a few frames. </p>
  
  <h2>The way I'm implementing the websocket</h2>
  
  <p>The way I'm developing it is something like a master slave communication. Whenever the client sends a string, the server decodes it and then answers. At the moment I'm simply responding to a character 'e', which is designed to be just a counter. The thing is that I implemented the websocket on the client side  to send 'e' whenever it receives a message and then displays the message on the page. </p>
  
  <h2>The problem</h2>
  
  <p>The problem is that it does about 15 transactions and then I can see the communication being re-transmitted from and to the stellaris board and then the communication closes. After the connection closes I noticed that that I can't access any other page on the board. It simply doesn't respond anymore. </p>
  
  <h2>My assumptions of what may be causing it</h2>
  
  <p>This lead me to believe that the transactions are being too fast and there may be an implementation bug, lwIP bug or hardware bug (I'm using the enet_io example as base).</p>
  
  <h2>My assumptions on how to fix it</h2>
  
  <p>After seeing this I can imagine that what I need is to control the string being sent to the microcontroller so that it sends once a second, or maybe even less, because at the moment it was doing something like 1000 transactions per second and sometimes more.</p>
  
  <h2>The question</h2>
  
  <p>So ... after my trials I still have a few questions that need to be answered. Do websockets need this kind of relationship? Where client asks and server serves? Or can I simply stream data from the server to the client as long as the connection is open? Is my supposition that slowing down my rates will work?</p>