Live data from Hacker News

My Node.js app, or, a simple explanation of asynchronicity and non-blocking IO

maryrosecook.com

11–14 of 14 posts

Re: My Node.js app, or, a simple explanation of asynchronicity and non-blocking IO

#11
post #2

Nice article, and an interesting combination of technologies! Maybe it's a little bit off topic, but I had a look at http://streethoarding.com/ to see the thing in action. I like the idea and execution (it runs pretty fast; very very simple design; would be interesting to see how well it runs with a huge amount of visitors) and as curious as I am (especially regarding security), the first thing I entered was some Jav…

Yes, HTML and script tags are left as is. People are in the middle of abusing this right now. My friend has just pointed out that the whole of jQuery is at everyone's disposal, too.

I'm learning javascript now. Just for this site. Awesome.

Re: My Node.js app, or, a simple explanation of asynchronicity and non-blocking IO

#12
Checking out your code it looks like you're just polling (not longpolling)? Instead of just holding the connection open and waiting for a new message you pass the latest message and let the client reconnect. I use node like this (really simplified but still): http://blog.dispostable.com/instant-mail-notifications-using...

Re: My Node.js app, or, a simple explanation of asynchronicity and non-blocking IO

#13

Checking out your code it looks like you're just polling (not longpolling)? Instead of just holding the connection open and waiting for a new message you pass the latest message and let the client reconnect. I use node like this (really simplified but still): http://blog.dispostable.com/instant-mail-notifications-using...

matthijs, really interesting post, and very much liked your product as well. Amazingly simple. But I couldn't see any new message indicator when I tried it out in Chrome. Has it already been put in production?

Re: My Node.js app, or, a simple explanation of asynchronicity and non-blocking IO

#14
post #13

Checking out your code it looks like you're just polling (not longpolling)? Instead of just holding the connection open and waiting for a new message you pass the latest message and let the client reconnect. I use node like this (really simplified but still): http://blog.dispostable.com/instant-mail-notifications-using...

matthijs, really interesting post, and very much liked your product as well. Amazingly simple. But I couldn't see any new message indicator when I tried it out in Chrome. Has it already been put in production?

Yes it is already live, all you need to do is click the "Check for new messages" button on the inbox page and you'll be notified with a sound and the new message will be highlighted.

I just checked and made sure it is still working as it is suppose to (Firefox + Safari). Ill try Chrome as well.

Post reply on HN