title: Accessing socket.io server via Apache served pages
body: <p>I hope this doesn't come across as a terribly silly question, but I'm learning how to implement a socket.io server for my website to produce real-time applications, but my problem is that I can't figure out how to implement said applications in an Apache served environment.  Currently, when I run <code>node server.js</code> to start my socket.io server, I have to access it by visiting <code>http://localhost:XXXX</code> where <code>XXXX</code> is whatever port I attach it to, naturally.  I don't want my website to be forced to be viewed on an alternate port like this, but I obviously can't attach the server to port 80 since Apache is listening on that.</p>
  
  <p>Obviously a natural solution would be to stop the Apache service and then node the server on port 80 that way to avoid a collision, but I don't want to sacrifice all of the functionality that Apache offers.  Basically, I want to continue to serve my website via Apache on port 80, and integrate certain aspects of real-time applications via socket.io on port 3000, let's say.</p>
  
  <p>Is there a way to do this that avoid the things I don't want?  Those things being 1) having users access my site with <code>:3000</code> in the URL, 2) disabling Apache, 3) using iframes.</p>
  
  <p>Thanks in advance.</p>