On Sun, Jul 10, 2016 at 2:03 PM, CVBruce <[email protected]> wrote:
> I still have concerns about this, and please don't take this as vote
> against, it isn't. In my last email I specifically mentioned the Windows
> implementation. I still haven't seen any mention on how we are going to
> make Windows work the same way as *NIX.
>
> We all know the saying Rexx Anywhere, Wrecks Everywhere. I don't think we
> want to create another instance where code works fine on one system and
> breaks on another.
> It sounds to me that since we are changing the *NIX code base and not
> changing the Windows code base to be similar in operation, then we are
> certainly opening ourselves to this possibility.
>
> I have used Rexx queues to communicate between processes that are running
> under different uids. I've used the rxqueue on Regina to communicate
> between processes running on different systems.
>
ooRexx already does not allow Rexx queue communication between different
uids.
Rick
>
>
> I mention this because this change would break those programs on *NIX
> systems. So it needs to be well documented in the release notes. It would
> also be nice if we could direct the users to other methods that can be used
> to achieve the functionality that we are removing.
>
> Bruce
>
> Sent by Magic!
>
> On Jul 9, 2016, at 1:39 PM, Rick McGuire <[email protected]> wrote:
>
> This looks interesting. I think it would be better to refactor the code so
> that the domain sockets are implemented by a separate class, leaving the
> SysCSSStream class still available if we have platforms where domain
> sockets are not an option. This was a much smaller change than I expected.
>
> Rick
>
> On Sat, Jul 9, 2016 at 3:46 PM, Moritz Hoffmann <[email protected]>
> wrote:
>
>> Going forward, I implemented unix domain sockets as a means of
>> communication on Linux. See attached patch. I didn't commit it as we first
>> need to reach consensus whether it should go into ooRexx 5 or not, but I
>> think it should. It would be great if someone else could adapt the Mac and
>> AIX code to make use of the changes once its committed.
>>
>> Cheers,
>> Moritz
>>
>> On Wed, Jul 6, 2016 at 4:14 PM Erico Mendonca <[email protected]>
>> wrote:
>>
>>> *De: *Moritz Hoffmann <[email protected]>
>>>
>>> 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.
>>>
>>>
>>>
>>> Hello Moritz,
>>>
>>>
>>>
>>> It should. MacOSX is BSD-based, and is a full-on UNIX certified system.
>>> In fact, you can even download, compile and install the whole BSD port tree
>>> of software on it, via MacPorts and other similar projects.
>>>
>>>
>>>
>>> --
>>>
>>> — Erico Mendonça
>>>
>>> Dedicated Support Engineer
>>>
>>> SUSE
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>
>
> ------------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
>
> ------------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
