strargs is now 'format'.

For string interpolation, use %s instead of %1. %(name)s is also supported.

* include.js pointed to the production resource.
* use_minified_version was incorrectly set to true.

cache busting: add 'enable_code_version' configuration - when true return 'code_version' in session_context - also /production/XXX_vYYY.{js,css} calls now map back to /production/XXX.{js,css} - issue #226

add version.js - a small abstraction which extracts a 7char abbrev sha from the current source - issue #226

always run our little node HTTP proxy locally to constantly test HTTP proxy support which we'll have in production - issue #904

add outbound HTTP proxy support to browserid - requires a proxy that can forward http to https traffic - closes #904

Adding i18n to wsapi. Split strings into client.po and messages.po.

Switched email from mustache to EJS templates.

Created fake locale db-LB for development and debugging.

Updated scripts.
See http://viewvc.svn.mozilla.org/vc?view=revision&revision=99911

simplify previous commit - .well-known/browserid really doesn't need a template and must be sent with application/json content-type - issue #865

return an error to the client when we cannot contact the keysigner.  (was just leaving the connection to hang...)

update wsapi_client to return errors in the standard node convention.  update all clients.  fix several areas in loadgen where we were not properly handling errors.  improve informational output of loadgen failures.  closes #838 - helps with issue #784 - closes #785

explicitly call .removeAllListeners() during http forwarding to eliminate memory leak.  closes #839 (with extreme prejudice)

explicitly call .removeAllListeners() during http forwarding to eliminate memory leak.  closes #839 (with extreme prejudice)

document in code where two level auth affect apis, specifically where you'll need to be password authenticated, vs. where assertion auth (with a primary address) is sufficient

(loadgen) fix bug that would leave virtual users with incorrect cookies in their device contexts after a password reset (still authenticated as th old user that they split from) issue #785

(loadgen) tons of fixes to handle request failures without mucking up the local user database - issue #838, issue #785, issue #787, issue #784

staging a new acct on a session logs you out.  clear the auth'd bit on the session when this happens to prevent errors that occur when the loadgen client thinks it's authed, but the server knows its not.  issue #785

gracefully handle excessive load - all cases where bcrypt will take to long return 503, loadgen special cases 503 errors for better output.  closes #787

updated to new version of client-sessions, renamed, and re-added connect-cookie-session for example primary

SCHEMA CHANGES! update the mysql driver to support the new database apis motivated by issue #388 (identify user by userid rather than email)

update all WSAPIs now that userid rather than email is stored in session after auth.  all tests pass on JSON database driver

update all database apis on the JSON side to interact in terms of user ids as the primary identifier rather than an email address.  first step toward migrating to userid in sessions instead of email addresses to solve issue #388 (and others like it) and pave the way for primaries

changed session over to benadida's node-cookie-session with encryption and signing of the cookie, closes #416, closes #832

perform password length checking everywhere a password is updated.  complete_user_creation now requires a 'pass' arg when the acct has no password (only primary accts)

email_for_token now returns whether the user must set a password to finish adding an email to their browserid account.  also write (failing) tests for imminent changes to complete_email_addition api.  also refactor db layer, adding haveVerificationToken to move code off of emailForVerificationToken that only cares about whether a verification token exists or not.  whew.

implement a 'maximum request time' for bcrypt work.  server now fails more gracefully under backbreaking load, returning 503s to clients of the authenticate_user api.  update loadgen to be less dramatic about, but still display, 503 errors.  first part of issue #787 - a partial fix for #785 in dere too

* All unit tests pass again.
* Renaming primary_user_verified to primary_user_ready
* Adding a random_seed to the context info to fix the unit tests and the adding of the seed.
* Renamed all ejs templates to match their URL.
* Each page unit test writes the ejs template that it needs to the DOM.