Home Applications InterJob-communication

InterJob-communication

This application is not supported by InterSystems Corporation. Please be notified that you use it at your own risk.
0
0 reviews
0
Awards
97
Views
0
IPM installs
3
1
Details
Releases
Reviews
Issues
Pull requests
Demo of IJC

What's new in this version

move to archive

Earlier I’ve written about command pipes.
This is the internal variant of a PIPE.

To make this more tangible and visible for you I prepared a small example
 
The scenario is to run a monitoring process that receives
input from an unknown number of sensors. 
(Could be Lab equipment or similar.) 

The monitor should not poll his sensors nor run
in a hang loop to scan a common global 
and work independently of any disk access. 
 
To try it log into a terminal 
.    DO ##class(IJC.Demo).%Start()  
The Highlander principle applies for this example: There can only be one  

Next open a new terminal and run
.    DO ##class(IJC.Demo).Sensor(“mytext”)
and see what happens.

It’s clear that for real applications:

  • the monitor might run in a background tasks
  • the sensors will do something useful.
    But this reduces visibility.

Article in DC

Made with
Version
1.0.216 Sep, 2023
ObjectScript quality test
Category
Technology Example
Works with
InterSystems IRISCachéEnsemble
First published
04 Dec, 2022
Last checked by moderator
01 Nov, 2023Works