Greetings all, I was thinking to ask to compare to the pre-ooRexx v4 way of handling RXAPI, however...
Moritz Hoffmann wrote: > I think a clean solution would be to use UNIX sockets on Linux and similar > systems. I don't know about Mac or Windows but I'm sure there exists > something equivalent. Then, each user would have its own > instance of the api daemon that is accessible using a socket stored in the > file system, either the user's home directory or a temporary directory. On > Linux, various tools use this: tmux stores its > socket in /tmp/tmux-$(id -u)/default. Adapting ooRexx to use such a schema > should be fairly easy. Moritz came up with thoughts in a different alternate direction than merely stepping backwards in time. So, parallel to Moritz's suggestion... Q: Did the old way of handling RXAPI actually work better than what we are now dealing with? Any good in improving upon the ooRexx v3.2 design in this area of the code? I am thankful, -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
