It has always been a pleasure to listen to you guys!
Keep on rocking!

ps. All kinds of real life situations that produce delays are allowed 😉

Ben Franklin once said: “Who you are speaks so loudly I can’t hear what you’re saying”.

Latin expression: Illegitimi non carborundum i >>>> “Don’t let the bastards grind you down”.

Justin and Jason > Great podcast > Keep up the good work.
Sincerely,
Michael.

Please don’t stop the show. I started late with the show but was hooked after listening a couple of episodes.

I learn so much from listening to you guys.

– From the Philippines… (see guys, you have an international following!)

I love the show. I hope you don’t lose faith and keep it up!

Have you looked into Namecoin (http://en.wikipedia.org/wiki/Namecoin)? Seems to resemble what you were talking about with DNS-based cryptocurrency, but it is based on the distributed model.

I really value listening to Techzing and it would be a sad loss for me if you stopped….not as bad as losing a limb, but close 🙂

Congrats on impending fatherhood Justin. Keep up the good work!

1. I learn a lot. Here’s a 5-minute clip of one of the most enduring lessons….in fact, the birth of a legitimate meme….from episode #59:
http://bitsbeensaid.com/BBSweb/Play.aspx?PCId=246

2. I laugh a lot. Here’s a 1-minute clip that makes me laugh every time (often!) I replay it….from episode #245:
http://bitsbeensaid.com/BBSweb/Play.aspx?PCId=636

As to the inevitable, occasional negative feedback you receive…..just today I saw this article regarding an internet scale “empathy vacuum”. I hope it’s a good read for Jason…..and a good skim for Justin. 😉
http://www.eod.com/blog/2014/02/empathy-vacuum/

Thank you for the podcast, the knowledge, and the good times!

~David~

After I did that change, we still had a memory leak, and when running the profiler it showed that ‘connect’ event takes a long time, so I figured I need to look more into socket.io problem.

I also tried most of the stuff described in this post series (Node.js w/1M concurrent connections):
http://blog.caustik.com/2012/08/19/node-js-w1m-concurrent-connections/

I started to go through socket.io issues on GitHub and found out a lot of people have/had memory leaks for different reasons, and some people just exposed the garbage collector and initiated it from their codebase every now and then. Doing that did help but I couldn’t really test it under real-life traffic so I don’t know how good it really is.

I came across a blog post (which is offline now, but the cached link is below) that showed a memory leak in socket.io/lib/manager.js in Manager.prototype.handleUpgrade method.

Link: http://web.archive.org/web/20130715225511/http://jpallen.net/2013/03/08/tracking-down-a-memory-leak-in-node-js-and-socket-io

The leak is in req.head variable. By the time I came across this post, there was already a “fix” for the leak.
The official “fix” for this leak was assigning null to the variable after some manipulation was done:

this.handleClient(data, req);
req.head = null;


but it wasn’t working, and I know that because after I added the line from the blog post:

delete req.head;

it worked fine (until we had another (smaller) issue regarding transports on certain devices).

Regarding the bad email:
A good quote from a movie you can use next time: “Argo f*ck yourself!”
No one forces anyone to listen to a podcast, your show, your call.

– Dylan

Please post the email.

Thanks,

Mohammed Firdaus