Having trouble with the Socket.IO Tutorial samples. Incomplete documentation or PEBCAK?

I should probably have mentioned that the reason I switched from the "documentation-provided" code was because that didn't work either. What I didn't try is "localhost:8000/socket.io/socket.io.js" rel="nofollow">localhost:8000/socket.io/socket.io.js"" rel="nofollow">localhost:8000/socket.io/socket.io.js" maybe socket. Io 'compiles' and server the client-code and adds its own url-transport to express.

– Alex C Sep 26 at 15:08 1 Yes, Socket. IO takes care of serving the client code. But /socket.Io/socket.io.

Js should be equivalent to localhost:8000/socket.io/socket.io.js" rel="nofollow">localhost:8000/socket.io/socket.io.js (assuming you are serving the HTML file from localhost:8000). – Daniel Brockman Sep 26 at 15:15 Thanks, I knew it was something simple. I'm definitely going to want to communication / socket server to be separate from the static files.

So I guess I was trying to run before I could walk. The static page was being served seperately, which complicated stuff. – Alex C Sep 26 at 15:58 OK.

Thanks for acceptance. Good luck! – Daniel Brockman Sep 26 at 16:01 Tested and verified - you actually serve the client side JS file through the socket itself.

So, if you're socket is on 8000 you pull the client side JS through localhost:8000/socket.io/socket.io.js" rel="nofollow">localhost:8000/socket.io/socket.io.js not the express default 3000 or whatever. – Alex C Sep 26 at 18:59.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.