Adds static process and refactors routing of WSAPI requests - issue #1757
The `static` process has been added to handle cachable resources and views, so code relevant to serving those resources has been removed from `browserid`. The `router` heartbeat now depends on both `browserid` and `static` processes being ok. `router` now forwards wsapi writes to `dbwriter`, reads to `browserid`, and errors on unkown or internal wsapi requests. The wsapi setup for `browserid` no longer handles forwards, though some wsapi operations may trigger a forward to `dbwriter`.
Showing
- bin/browserid 10 additions, 35 deletionsbin/browserid
- bin/dbwriter 2 additions, 2 deletionsbin/dbwriter
- bin/router 20 additions, 9 deletionsbin/router
- bin/static 106 additions, 0 deletionsbin/static
- config/local.json 1 addition, 0 deletionsconfig/local.json
- config/production.json 3 additions, 1 deletionconfig/production.json
- lib/browserid/views.js 2 additions, 0 deletionslib/browserid/views.js
- lib/configuration.js 4 additions, 0 deletionslib/configuration.js
- lib/wsapi.js 102 additions, 96 deletionslib/wsapi.js
- lib/wsapi/create_account_with_assertion.js 1 addition, 1 deletionlib/wsapi/create_account_with_assertion.js
- scripts/run_locally.js 2 additions, 0 deletionsscripts/run_locally.js
- tests/heartbeat-test.js 60 additions, 0 deletionstests/heartbeat-test.js
Loading
Please register or sign in to comment