Mikkel Schmidt

Yea sorry i sort of forgot about this again. I'll take a look at it sometime this week!

I just published 0.2.0. Please check if it works as expected :) see 6c1bbc1f003273bc3d6ed2554b7cce71f69d5e0f for implementation details. Also i've updated the docs to include command line arguments / npm config...

Oh i almost forgot. Be aware that the default ports have changed to allow for x64 on osx and windows. ##### Server socket ports: - osx32 servers will use 3001...

@chino23 Have you had a chance to check it out yet?

Yes, i put it in so you know what happens. Although this: ``` Using socket port from npm package configuration: #{config.sockPort} Using http port from npm package configuration: #{config.httpPort} ```...

Just published 0.2.1, please try again. It should work as before though, but i did mess up in a few places.

You did update your servers too right? Are you running the server(s) in a VM? If that's the case, did you remember to forward the right ports?

Right, then updating the package is enough (was thinking you might use VM's). Well, then i'm sorta stumped. The tests run fine (they connect to the server locally too). Does...

I have LOTS of intervals and timeouts, and a lot of code (nearly breaking the limit on x64). I have had no problems with it at all. The performance is...

Put them in you index.html, so you're sure they're loaded. I'll run som tests on 11.x in the mean time.