woozyking

Over the time of learning and practicing various programming techniques, on personal and organizational projects, I have developed a discipline on the way I code - I should code for my users.

In a recent project, I needed to maintain quite a number (8-9 and growing) of charts that support “real-time” data updates (1 second interval) on a single page. The following open source libraries are what I have tried.

I had a simple problem along the way of exploring Node.js, which involves writing modules that work for both server and client sides. Just like many programmers nowadays, I google’d out a solution (which was written by the person who authored async, so I guess I need to thank him at least twice).

However this doesn’t solve all my problem since I am way too lazy to get rid of all those amazing open source libraries.

“Yes, you have my full attention right now.”

TL;DR: Archive emails (ham), with discipline.

I have been toying around with a few ideas lately, the process allowed me to tackle some interesting problems by ways that are not so conventional, at least not the ones from Google page 1’s.

I was joking the other day, that by looking at the current Ubuntu version number, one could realize how fast time goes by.

Though I believe these time based concepts are just illusions that human beings created, that I would rather not let them clutter my mind as other unworthy things, they matter in the real world, or meta world that I would like to call it.

It was about the same time when I got into the amazing worlds of programming and strategy games, when I was about 16 years old.

Ten years later, I’ve figured out some astonishing similarities between them.

Previously, we discussed the possibility to hack PycURL to achieve somewhat a more controllable HTTP streaming client.

Today, let’s add some Redis ingredients into our recipe and make this tool more controllable so that we can solve the remaining problems aforementioned.

Recently I needed to have something that allows me to have more control over my data stream client, so that:

1. When desired, it would stop and close the connection as gracefully as possible.
2. A precise counter for how many records have been received is in place.

The initial implementation was quite straightforward:

As mentioned earlier, I finally dropped virtual host and rented myself a Droplet. It’s cheap, easy to setup, no downside yet (except that it’s a really small instance compare to what I work with during day times).

I’ve wanted to move our xiangpi.ca to a VPS for a long time now since I don’t like Wordpress without heavy optimizations. With a virtual host there wasn’t much I could do.