Troplo/node-ipc
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Wiki Activity

Merge branch 'master' into patch-1

Browse source
This commit is contained in:
Brandon Nozaki Miller 2021-07-01 15:52:17 -07:00 committed by GitHub
commit 4a513eebad
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
README.md
View file

@ -56,7 +56,7 @@ You may want to install jasmine and istanbul globally with ` sudo npm install -g
4. [IPC Events](#ipc-events) 4. [IPC Events](#ipc-events)
5. [Multiple IPC instances](#multiple-ipc-instances) 5. [Multiple IPC instances](#multiple-ipc-instances)
6. [Basic Examples](#basic-examples) 6. [Basic Examples](#basic-examples)
1. [Server for Unix||Windows Sockets & TCP Sockets](#server-for-unix-sockets--tcp-sockets) 1. [Server for Unix||Windows Sockets & TCP Sockets](#server-for-unix-sockets-windows-sockets--tcp-sockets)
2. [Client for Unix||Windows Sockets & TCP Sockets](#client-for-unix-sockets--tcp-sockets) 2. [Client for Unix||Windows Sockets & TCP Sockets](#client-for-unix-sockets--tcp-sockets)
4. [Server & Client for UDP Sockets](#server--client-for-udp-sockets) 4. [Server & Client for UDP Sockets](#server--client-for-udp-sockets)
5. [Raw Buffers, Real Time and / or Binary Sockets](#raw-buffer-or-binary-sockets) 5. [Raw Buffers, Real Time and / or Binary Sockets](#raw-buffer-or-binary-sockets)
@ -480,7 +480,6 @@ or specifying everything UDP
|destroy||triggered when socket has been totally destroyed, no further auto retries will happen and all references are gone.| |destroy||triggered when socket has been totally destroyed, no further auto retries will happen and all references are gone.|
|data|buffer|triggered when ipc.config.rawBuffer is true and a message is received.| |data|buffer|triggered when ipc.config.rawBuffer is true and a message is received.|
|***your event type***|***your event data***|triggered when a JSON message is received. The event name will be the type string from your message and the param will be the data object from your message eg : ` { type:'myEvent',data:{a:1}} ` | |***your event type***|***your event data***|triggered when a JSON message is received. The event name will be the type string from your message and the param will be the data object from your message eg : ` { type:'myEvent',data:{a:1}} ` |
||||
### Multiple IPC Instances ### Multiple IPC Instances