Obsolete
/
libipc-old
Archived
3
0
Fork 0
Code

ébauche de README

more_to_read
Philippe PITTOLI 2016-09-13 21:56:39 +02:00
parent 85c5d97bad
commit 71de2482c6
1 changed files with 22 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
README.markdown
View File

@ -1,43 +1,44 @@
# connection init (draft) # connection init (draft)
## what the programs should do and how they interact ## how things happen
* service : application providing a feature to others (windows, audio, …) * Service : daemon providing a feature (windowing, audio, …)
* program : specific application (browser, instant messaging, …) * Application : specific application (browser, instant messaging, …)
* [service] : service name * [service] : service name
* [index] : process index in the program point of view * $pid : application PID
* [pindex] : process index in the service point of view * $index : process index (application point of view)
1. the service creates a pipe, named /tmp/[service] 1. Service creates a pipe named /tmp/[service]
2. the program creates pipes named /tmp/$pid-[index]-{in,out} 2. Application creates pipes named /tmp/$pid-$index-$version-{in,out}
3. the program prints in the pipe /tmp/[service] : $pid-[index] version 3. Application sends in /tmp/[service] : $pid $index $version
4. depending on the configuration and service type, the service will
* thread, to spare resources
* fork, not to compromise the security
5. the service prints [pindex] in /tmp/$pid-[index]-in
## pure "networking" view (what should go in the pipes) ## pure "networking" view (what should go in the pipes)
1. the program prints in the pipe /tmp/[service] : $pid-[index] version 1. Application sends in /tmp/[service] : $pid $index $version [...]
2. the service prints [pindex] in /tmp/$pid-[index]-in
# messages format # messages format
QUESTION : no CBOR for 1 & 2, or CBOR everywhere ? 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)][cbor].
This will be used with some conventions.
## overview ## overview
format "type : value" The format will be "type : value".
type will be a simple byte : The type will be a simple byte :
* <0 - 15> : control, meta data * <0 - 15> : control, meta data
* <16 - 127> : later use * <16 - 127> : later use
* <128 - 255> : application specific (windowing system, audio system, …) * <128 - 255> : application specific (windowing system, audio system, …)
## CBOR table (TODO) ## CBOR type convention
index | semantic 0 - 15
index | abbreviation | semantic
0 | close | to close the communication between the application and the service
[cbor]: https://tools.ietf.org/html/rfc7049