[Info-vax] VMS process communication

[Marc Van Dyck]

Arne Vajhøj formulated on Tuesday :
> I did a little writeup:
>
> https://www.vajhoej.dk/arne/articles/vmsipc.html
>
> Content:
>
>      Introduction
>      Shared Memory
>          Concept
>          Demo
>          System Service (C, Fortran, Pascal)
>      Memory Mapped File
>          Concept
>          Demo
>          System Service (C, Fortran, Pascal)
>      Writeable Shareable Image
>          Concept
>          Demo
>          Linker/installer (Fortran, Pascal, C, Basic)
>      TCP/IP Socket
>          Concept
>          Demo
>          Java API (Java)
>          C API (C)
>          Python API (Python, Jython)
>          Wrapper C API (Fortran, Pascal, Cobol, Basic)
>      Message Queue
>          Concept
>          Demo
>          JMS API (Java, Jython)
>          STOMP C library (C)
>          STOMP Python library (Python)
>          Wrapper C STOMP library (Fortran, Pascal, Cobol, Basic)
>      Index Sequential File
>          Concept
>          Demo
>          Language builtin (Pascal, Cobol, Basic, Fortran)
>          RMS API (C)
>          VMS Python IndexedFile (Python)
>          JVM ISAM library (Java, Jython)
>      SQLite Database
>          Concept
>          Demo
>          C API (C)
>          Python API (Python, Jython)
>          JDBC API (Java)
>          JPA API (Java, Jython)
>          Wrapper C API (Pascal)
>
> Arne

Should layered/third party products like RTR, DEC MessageQ or even
MQ Series (and its Opensource equivalents) be mentioned in such a work
too ? Honest open question, not saying that they are missing...

-- 
Marc Van Dyck