title: Node.js TCP incoming message splitting into packages
body: <p>I have a problem when receiving large packets in Node.js through a TCP connection.
  It seems that there is a cap in the buffer set to about 55kB. When I receive large amounts of data (about 70-80k) it splits this data up.</p>
  
  <p>Now, I've worked with UDP sockets, I know how to expect <code>on('data', function(){})</code> events and how to expect an <code>on('end', function(){})</code> when the message is finally received, the problem with the TCP is that I never receive an <code>on('end', function(){})</code> event, the server (in C#) never sends a FIN packet. This is due to me requiring to keep the socket alive and ongoing (we don't want to shut it down).</p>
  
  <p>Is there some sort of way to send a FIN packet, from the C# to the Node.js one, without having to shut down/close the socket?</p>
  
  <p>Or, alternativelly, is some sort of way to trigger the <code>on('end', function(){})</code> event inside node itself?</p>
  
  <p>Regards.</p>
  
  <p><strong>EDIT:</strong>
  To add up to the question, say for instance I have 2 clients attempting to acquire information through the TCP socket. One connects first, and gets a huge request (no problem on the size here).</p>
  
  <p>But whilst this request is being handled, another one does the same request, since the TCP connection is through node, they're using the same socket.
  Is there any way to differentiate the requests? or will I have to set up a socket for each request being done to the TCP server?</p>