- Validator class now takes care of all the validations.
- Request class implements the actual requests performed.
- TableFactory sets up all database connections and provides access to
  Table classes.

Performs queries to:

- retrieve all targets a user has subscribed to.
- retrieve all users who have subscribed to a target.

Added Comments#showVoteDirBy method to set the user who's vote
directions are shown when using the #get #find and #findRecent.

To be able to query the deleted comments, the Comments#showDeleted
method can be called to define whether deleted comments should be
included to the query.  This is implemented through having two
views in the database: full_comments and full_visible_comments.

Added triggers to database to recalculate the comments.vote column when
votes table is updated.

Plus minor fix to test data.

Allows first phase in comment editing - popping up the editor.

Added requireLogin service.
Added _id field to comments response.

When doing #add or #update the content_html field is generated from
content field.

Performs formatting of comments markdown.

Instead of listing all target properties inside the comment object
separately, there's now a target property that should contain object
with type,cls,member fields.

Created Users class, which uses the ForumAuth to first log in through
Sencha Forum and then when needed creates entry to users table in
comments database.

The main thing is that now the user object stored into session contains
an `id` field which we can use in further queries to add/update/delete
comments.

It's responsibility is to convert between DB structures and the JSON
objects that out HTTP API expects.

Turn off logging of what MySQL session store is doing.

Instead enable logging of HTTP requests that our express server gets.

Simple initial implementation.

Responds to auth and comments_meta requests.

With /auth we always respond with false.

With /comments_meta we only return comment counts.

Make the data structure the same as in old comments app.

On error the rows will be null, so do a check before calling rows[0].

Finally understood why it's the convention in NodeJS.
So following it now.

I assume this is more along the lines how things are done in NodeJS.

So the actual interfacing with node-mysql is contained within that
class.

The :jasmine task now populates comments_test with test data and
then runs the testsuite against it.

The script update_votes.sql calculates the values for that column based
on the entries in votes table.

This is an optimization to avoid aggregating the votes in a separate
table every time we retrieve comments.

Also updated examples.sql to use the new full_visible_comments view -
this greatly simplified all queries.