Hatch as browser native messaging host
Bug #1640255 reported by
Bill Erickson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Bill Erickson |
Bug Description
Teach Hatch to act as a browser Native Messaging request handler. This lets us run and communicate w/ Hatch via browser extension via STDIO instead of WebSockets, obviating the need for Jetty, SSL certificates (valid or otherwise), and the specter of a disappearing websockets-
More discussion to follow. In the meantime...
https:/
https:/
Work in progress:
To post a comment you must log in.
Webstaff bits updated here:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1640255- hatch-native- messaging
Using the 2 branches listed in this bug, I'm able to communicate w/ Hatch via Native Messaging using the same API as before. Initial tests show printing to be more stable with the Hatch internals overhaul.
TODO: how-to docs so others can experiment.