https://github.com/as400jplpc/nim_msgshm

Single communication area between programs or between threads
https://github.com/as400jplpc/nim_msgshm

communications msgshm nim nim-lang

Last synced: 10 days ago
JSON representation

Single communication area between programs or between threads

• Host: GitHub
• URL: https://github.com/as400jplpc/nim_msgshm
• Owner: AS400JPLPC
• Created: 2021-11-16T00:46:34.000Z (about 3 years ago)
• Default Branch: master
• Last Pushed: 2021-11-17T09:34:24.000Z (about 3 years ago)
• Last Synced: 2024-11-28T10:30:26.697Z (2 months ago)
• Topics: communications, msgshm, nim, nim-lang
• Language: CSS
• Homepage:
• Size: 33.2 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# nim_msgshm

Single communication area between programs or between threads 

Hello,

the goal is to be able to communicate between two or more programs or between threads.

functions:  

  

msgget  ---> opening shared communication area   

  

msgsend ---> send message  

  

msgread ---> get message and len   

  

getNbrMsg -> get number message  

  

  

msgctl  --->  close and delete zone communication  

  

doc : [MSGSHM](http://htmlpreview.github.io/?https://github.com/AS400JPLPC/nim_msgshm/blob/master/htmldocs/msgshm.html)

  

example :  

  

msgq01 msgq02  

  

  

api "C"  to connect module nim
   

  

respect process type Linux and os400 unix   

  

data len max 1024 *all character  

  

  

For the realization I relied on the documentation: 

IBM ZOS 

LINUX system development under Linux (Eyrolles) 

advanced NIM documentation  

doc : [SOURCE](https://github.com/AS400JPLPC/nim_msgshm/blob/master/exemple/msgq01.nim)

doc : [SOURCE](https://github.com/AS400JPLPC/nim_msgshm/blob/master/exemple/msgq02.nim)

message  friend :)

Suddenly, if I understood correctly, it is network communication on the local loop between threads within the same process, 

so that it is practical, simple to implement and quite flexible.

=> There is no limitation of signals under linux (signals already dedicated or not very customizable)

=> no need to configure and implement (and therefore maintain) a message bus system.

=> The message mechanism leaves flexibility, with a limitation of 1024 characters but which precisely 

allows not to have messages that would contain huge clusters of data 

(it is not made for, by design, which de facto maintains the performance )