update
This commit is contained in:
@@ -456,7 +456,7 @@ BridgeSwarm consists of three main parts working together:
|
|||||||
|
|
||||||
## Finding the Way In
|
## Finding the Way In
|
||||||
|
|
||||||
Chrome extensions have this feature called native messaging. It's been around since the early days, but the official documentation focuses on mundane use cases: integrating with password managers, connecting to desktop notification systems, that sort of thing. The technical capability underneath is much more powerful.
|
Chrome extensions have this feature called native messaging. It's been around, but the official documentation focuses on mundane use cases: integrating with password managers, connecting to desktop notification systems, that sort of thing. The technical capability underneath is much more powerful.
|
||||||
|
|
||||||
Native messaging lets an extension spawn a process outside the browser and communicate with it through standard input and standard output. The browser handles spawning the process, manages its lifecycle, and provides a clean message-passing interface. Nothing fancy, but effective.
|
Native messaging lets an extension spawn a process outside the browser and communicate with it through standard input and standard output. The browser handles spawning the process, manages its lifecycle, and provides a clean message-passing interface. Nothing fancy, but effective.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user