search

lysol / typeto.me

character-level realtime chat
http://typeto.me
MIT License
19 stars 7 forks source link

Fails behind a VPN #1

Closed dmd closed 13 years ago

dmd commented 13 years ago

My test user behind a VPN never sees herself as connected.

Alternatively she sometimes sees herself as connected even though nobody else is there!?

lysol commented 13 years ago

Committed my changes that should fix this, pushing live. Test in a little while, see if this is solved.

lysol commented 13 years ago

Site is currently broken, looks like Apache doesn't play nice with socket.io. Think I need to set up a bare node.js instance somewhere to really do this up right.

dmd commented 13 years ago

What kind of resources? http://www.lowendbox.com/blog/vpsvibe-3-99-256mb-openvz-vps-in-chicago/ is ubercheap ... how many concurrent sessions do you think a slice like that could handle?

lysol commented 13 years ago

Closing this because we now don't care about VPNs.

dmd commented 13 years ago

We probably SHOULD care if we want wide acceptance. We can fix this by running on a slice like above, right?

Or am I missing something here?

lysol commented 13 years ago

Yes. If we throw it on port 80 and run node front and center and not proxied behind a web server it'll work fine. More of an implementation detail than a code issue, because the code can already handle this.

On Aug 16, 2011, at 1:55 PM, dmd reply@reply.github.com wrote:

We probably SHOULD care if we want wide acceptance. We can fix this by running on a slice like above, right?

Or am I missing something here?

Reply to this email directly or view it on GitHub: https://github.com/lysol/typeto.me/issues/1#issuecomment-1819195

dmd commented 13 years ago

Up on rackspace now, should solve this issue.