#inter-process #ipc #io

gipc

A generic abstraction layer over raw sockets for interprocess communication, with async support

3 unstable releases

0.2.0 Jul 14, 2023
0.1.1 May 7, 2023
0.1.0 Apr 30, 2023

#24 in #inter-process

Download history 6/week @ 2024-02-20 25/week @ 2024-02-27 9/week @ 2024-03-26 42/week @ 2024-04-02

51 downloads per month

MIT license

29KB
520 lines

General Interprocess Communication

General Interprocess Communication (or gipc, pronounced like gypsy /ʤɪ́psɪ/) is a library that abstracts away common things in interprocess communication to speed up development and reduce errors.

NOTE:

gipc is not entirely stable yet - there are still a few wrinkles to iron out. Whilst it is production-ready, the API may be subject to change.

Usage

To get a sense of how to use gipc, please read the examples; these show roughly how the code would look in an application, alongside explanations of why everything happens in the order that it does.

If you don't want to do that, that's fine! The crate's documentation should be sufficient to give you a starting point, although it's probably not as good as the examples.

Licence

gipc is licensed under the MIT License. You can find the licence text in LICENCE.


lib.rs:

General Interprocess Communication (or gipc) is a library that abstracts away common things in interprocess communication to speed up development and reduce errors.

See the connection module for info on how to get started.

Crate structure

The connection module handles all things related to receiving and sending data between your programs. This is aided by the message module, which describes the communication protocol that it uses.

Any errors the crate can return are in the error module.

Dependencies

~1–13MB
~123K SLoC