Obsolete
/
libipc-old
Archived
3
0
Fork 0
OLD IMPLEMENTATION. The new one is in Zig and fucking ROCKS: https://git.baguette.netlib.re/Baguette/libipc Inter-Process Communication library based on unix sockets.
This repository has been archived on 2024-06-18. You can view files and clone it, but cannot push or open issues/pull-requests.
 
 
 
 
 
Go to file
lapupe cb442e7218 tcpdserver deleted 2016-09-16 00:12:39 +02:00
lib adapted pingpong apllication for the new version ex: pid-ind_in -> pid-ind-ver-in 2016-09-15 15:34:56 +02:00
misc updates in misc/ and new (future) program "msg" for CBOR msg 2016-09-14 23:05:02 +02:00
pingpong adapted pingpong apllication for the new version ex: pid-ind_in -> pid-ind-ver-in 2016-09-15 15:34:56 +02:00
pubsub updates in misc/ and new (future) program "msg" for CBOR msg 2016-09-14 23:05:02 +02:00
remote tcpdserver deleted 2016-09-16 00:12:39 +02:00
.gitignore gitignore : .o 2016-06-06 01:55:31 +02:00
Makefile Makefile update. 2016-09-02 21:43:19 +02:00
README.markdown ébauche de README 2016-09-13 21:56:39 +02:00
project.zsh Makefile update. 2016-09-02 21:43:19 +02:00

README.markdown

connection init (draft)

how things happen

* Service : daemon providing a feature (windowing, audio, …)
* Application : specific application (browser, instant messaging, …)

* [service] : service name
* $pid : application PID
* $index : process index (application point of view)

1. Service creates a pipe named /tmp/[service]
2. Application creates pipes named /tmp/$pid-$index-$version-{in,out}
3. Application sends in /tmp/[service] : $pid $index $version

pure "networking" view (what should go in the pipes)

  1. Application sends in /tmp/[service] : $pid $index $version [...]

messages format

First of all, the application will send a message to the service's pipe in plain text with its PID, the number of time the process already used the service (index) and the version of the communication protocol we want to use between the application and the service.

In order to communicate between the application and the service, we use the CBOR format (RFC 7049). This will be used with some conventions.

overview

The format will be "type : value".

The type will be a simple byte :

* <0 - 15>   : control, meta data
* <16 - 127> : later use
* <128 - 255> : application specific (windowing system, audio system, …)

CBOR type convention

0 - 15

index   | abbreviation  | semantic
0       | close         | to close the communication between the application and the service