#chrome #native #messaging #host #protocol

chrome_native_messaging

Implementation of Chrome's Native Messaging protocol

5 unstable releases

0.3.0 Jun 27, 2022
0.2.0 Jan 7, 2021
0.1.2 Dec 12, 2017
0.1.1 Jun 27, 2017
0.1.0 Jun 27, 2017

#11 in #event-loop

Download history 4/week @ 2023-11-02 2/week @ 2023-11-09 9/week @ 2023-11-16 7/week @ 2023-11-23 24/week @ 2023-11-30 3/week @ 2023-12-07 8/week @ 2023-12-14 10/week @ 2023-12-21 3/week @ 2023-12-28 6/week @ 2024-01-04 27/week @ 2024-01-18 13/week @ 2024-01-25 28/week @ 2024-02-01 44/week @ 2024-02-08 96/week @ 2024-02-15

181 downloads per month

MIT/Apache

9KB
117 lines

Chrome Native Messaging in Rust

Google Chrome allows native applications to interface with browser plugins as described in their documentation. This Rust crate provides simple functions for encoding/decoding JSON messages and handling errors during this process.

API Documentation

License

Licensed under either of

at your option.

Contribution

  • It would be great to integrate this with Tokio in order to make a fully asyncronous event loop. I haven't needed it personally so far, therefore it hasn't been worth my time to implement it.
  • Currently there are no integration tests with Chrome itself, to make sure that the protocol is implemented correctly. I wasn't sure how to achieve this easily, but if anybody has a suggestion then it would be welcomed.
  • All contributions/suggestions welcome!!

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Dependencies

~0.7–1.5MB
~35K SLoC