Added combined X509MixMatchAuthenticator, which allows for logging in both clients with hostname cert and with client name cert

Fixed first client's access without id (IndexError: tuple index out of range) (thanks to Radko Krkos)

getEvents - id<=0 now resets server's notion of client's id to last N events (and starts sending there)

 * Server is now in line with Idea spec concerning client names - they are stored in db and compared lowercase
 * Fixed duplicity check when adding/modifying client
 * Secret is not secret anyway, simplify Client and logging code

* fixed missing 'dml' modifier in some queries

Server now limits max accepted event size. events.data changed to longtext to accomodate longer events

Server now silently logs and skips events which cannot be deserialized from db. That can happen if too big event slips in and db truncates it, causing invalid JSON.

* help message fix

 * Changed charset to utf8 (not mb4, to support older MySQLs) in sqldump
 * Ditched data from clients (no predefined clients for new installations) in sqldump
 * Identity is renamed to name everywhere ii code and db to be consistent with Idea terminology
 * Better exception handling in insertLastReceivedId

* Fixed initialization logging

On MySQLdb (1.2.2) we still experience stale uncommitted transactions and different warden_server processes don't see actual db data. Looks like there is at least one stale transaction per daemon, appearing at any call to execute. I have no better idea than to implicitly commit after each SELECT (INSERTs are committed/rolled back explicitly).

* warden_server: Added "events_id" key into errors along with "events" - makes error messages bigger, but allows client operators to identify offending messages by stable identifiers based on logs.
* Removed too much internal info from database errors.
* Removed format type checking from Draft4Validator, using only explicit schema regexps - Draft4Validator raised FormatError istead of ValidationError, rendering iter_errors unusable.
* warden_client: Implemented retries on server errors.
* Client now honours send_events_limit from server - too long list of events is split and sent in chunks.
* getInfo and sendEvents update local send_events_limit according to one sent by server in info or error message.
* Logging is now explicit, not authomatic in Error class, allowing to log only single time at top level methods.
* More sane default client name.
* Errors from server are now checked and ensure correct format.
* warden_filer: Ditched error and retry handling, warden_client now does for us.

Reworked error handling in server, client and filer (again :( ). We definitely have to support multiple errors so let's do it right.  Error now contains list of errors.  Got rid of "detail" section everything now goes directly within particular error.  Error can bear "events" attribute for list of sent events concerned (or none if all sent events erred). Streamlined error logging.
Server now retries if MySQL went away.
Response result now gets properly encoded if Unicode appears somehow (however that's just fighting symptoms, should get more thorough fix).

syntax highlighting. :) (deja-vu)

or rolled back. insertLastReceivedId was not committed, and as we reuse the cursor, reader
client kept getting stale data until next event insert on the same connection, possibly
from completely different client at completely unrelated time (which unintentionally
closed even the previous transaction), or until server restart. Whew, tricky beast to hunt.

  consistently. Possible keeping and reopening where possible will need more
  work and testing, I'm not keen to try to clench in now. So - changed to
  reopening connection each time, which will possibly affect performance (on
  small queries).
- Both server and client library now defaults to get_events_limit instead of 1

Fixed Recon id in catmap
Fixed isoformat calling on None
Shortened validation error message
Fixed rejecting of Test messages