I'm reworking the rxapi daemon process to no longer use AF_INET sockets for IPC but rather use AF_LOCAL sockets. The new daemon processes will be specific to the user and bind to a user-specific name so that there will be one daemon per Rexx-using user.
The service names have to be bound into the the file system, but I'm not finding a lot of guidance on where these files should be placed. One approach that will work would be to use something like /tmp/oorexx/5.0.0-64/username Where each logged in user gets it's own unique service. However, I'm wondering if it might be better to use something like ~/.oorexx/5.0.0-64 Where a hidden file in the user's directory space is used. This might be a little more secure, since another process can only connect to the socket service if it has read/write permissions to the bound file. Note that with this new setup, a user will be able to run multiple releases if they wish or even use both the 32- and 64- bit versions at the same time. Do this make sense? Can the "~" form be used on the bind? Rick
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
