Hopiu/postal.js
1
0
Fork 0
mirror of https://github.com/Hopiu/postal.js.git synced 2026-03-16 22:20:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated node sample project readme with corrections

Browse source
This commit is contained in:
Jim Cowart 2012-09-24 09:53:42 -04:00
parent 20a2f6fd23
commit acaa28c06e
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
example/node/README.md
View file

@ -18,8 +18,8 @@ Open a terminal/console to the example/node directory and run `npm start`. Then
* You'll see postal.js used in node.js and in the browser (#winning?)
* This is way beyond a hello world example
* The browser and node.js postal instances are being *bridge* by a websocket connection (geek brownie points, FTW)
* I demonstrate a general usage pattern I've fallen into with the node.js side of things, which I call "Local message bus at boundaries, events internal."
* The browser and node.js postal instances are being *bridged* by a websocket connection (geek brownie points, FTW)
* I demonstrate a general usage pattern (message endpoint) I've fallen into with the node.js side of things, which I describe as "Local message bus at boundaries, events internal."
* Note that the node/messaging/ folder contains "bus-adapter.js" and "collector-adapter.js"
* These modules exist to adapt other bus-agnostics modules to postal.js
* The "bus agnostic" modules (for ex. - anything in the "collectors" directory) can work just fine without a message bus in place, but any subscribers would have to have a direct reference to the module, causing the application to be more tightly coupled.