Esprima now rejects those pieces of code as invalid JavaScript.

The new esprima no more considers newlines as part of line comments.

Let Esprima have its window object - otherwise it'll just crash.

We could simply query the forum database every time we need the e-mail
address, but I think it's better to keep interaction with forum database
to a minimum.  Besides, changing the e-mail address happens very rarely
and at least we now have this case covered.

This way we can take advantage of automatic updating of the created_at
fields and don't need to insert new Date() into all of those columns.

The old comments backend worked just fine with one shared connection, so
we shouldn't get quickly into troubles with this approach.

Previously the number of open connections just kept growing and growing
because they never got closed.  At least this problem is now gone -
there's just one open connection which we never close.

- Actaul application files go to comments/lib/
- Jasmine tests go to comments/spec/

The e-mail sender we use is configurable in ./config.js.

- 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.