status-im
/
realm-js
mirror of https://github.com/status-im/realm-js.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
realm-js/examples/NodeInterprocess
History
Adam Fish 842e5e3476 Minor tweaks to README language and folder name 2016-11-15 22:49:22 +01:00
..
README.md Minor tweaks to README language and folder name 2016-11-15 22:49:22 +01:00
index.js Minor tweaks to README language and folder name 2016-11-15 22:49:22 +01:00
listener.js Minor tweaks to README language and folder name 2016-11-15 22:49:22 +01:00
package.json Minor tweaks to README language and folder name 2016-11-15 22:49:22 +01:00
winston-realm.js Minor tweaks to README language and folder name 2016-11-15 22:49:22 +01:00

README.md

Realm-JS Interprocess Example

Example of interprocess support using Realm and Node.js

The example makes use of Winston, a logging library, and includes winston-realm.js which defines a custom transport utilizing Realm for storage. The main file, index.js is an Express app handling HTTP requests. The app listens on port 3000 and responds with "Hello World!" at the base path / and logs at info "Handled Hello World" to Winston. At any other path it returns a 404 error and logs an error message to Winston with URL in question.

Since the log messages are being stored in a Realm (winston.realm), we can listen for changes on another process. The listener.js is a small example of this. When running, this listens to the winston.realm for changes and writes to the console the latest error level log message.

To test:

  1. npm install
  2. node . to run the Express app
  3. In another process: node listener.js
  4. Go to http://localhost:3000/whatever to see error message across processes