BradChen.com

I have an upcoming research project, that I have to do for the BTR820 course at Seneca. Since there has been a revolution of NoSQL databases and polyglot persistence in recent years, this research project is a perfect opportunity for me to learn about various NoSQL databases.

The ultimate goal of the research project is to explore the applicability of polyglot persistence. I plan to examine and compare the programming model imposed by different types of NoSQL databases, and contrast them with traditional relational databases. The idea is to look at how application code would be written for each of the databases, and how the development of application would be impacted. I may also be exploring the philosophies and algorithms behind the data storage engines. If scope permits, I may possibly be looking at the management and security facilities provided by each, since these have impact on application development as well. Performance and horizontal scaling, e.g. clustering, however, will not be my focus.

Today I’m hit with the issue that Spring whines about the exception, “No Scope registered for scope 'request',” when I try to run tests with request scoped bean. Fortunately the fix is fairly easy.

Recently I have been trying to build the ability to send e-mails in a JSF project. Since Facelets is a great templating technology, I want to render the e-mails with Facelets. To my surprise, this isn’t an easy thing to do.

With the release of Processing.js v1.1, a very interesting feature was added — support for Webkit touch events. At the moment, there doesn’t seem to be any documentation on how these events can be used. (A ticket for this documentation bug appears to exist.)

For bug discussed earlier in here and here, here is the Mochitest.

Update July 18, 2011: Virgo 3.0.0.M05 upgrades Spring Framework 3.0.5. Steps documented here are no longer necessary.

After upgrading Virgo Web Server to 3.0.0 M03, I wanted to upgrade String Framework’s version from 3.0.0 to 3.0.5. Although this upgrade is on Virgo’s roadmap to 3.0.0, it won’t land for a few more weeks.

Following the last post on Image Map and HTML5, there has been some interesting development. Namely, the algorithm for dealing with a list of numbers isn’t as simple as it seems.

As a part of the DPS909 course, students were asked to work on Firefox bug #565031. This bug has to do with whether or not different kinds of white space characters should be treated as separators in an image map’s coords attribute. Well, it sounds really trivial — so trivial that fixing it simply isn’t a good use of a developer’s time. Therefore, this is a perfect opportunity for students to take a stab at.

Last week at Seneca’s DPS909 course, students were asked to modify Firefox’s chrome behaviour. I was also supposed to do this and blog about it, but other assignments of high priority simply forced me to procrastinate. Well, that’s no excuse, so here I am, blogging something about it.

Recently I have been building a small chat room application, using jQuery for Ajax and RESTEasy for server-side RESTful services. Because Java is used for the server side, and PHP is used to render the JavaScript for the client side, I need to use cross-domain Ajax calls. Like Flash, Ajax imposes security restrictions for such remote invocations. Here, I’m documenting the problems and solutions I have.