Re: [Oorexx-devel] RexxQueue user-specific on Windows

2018-07-26 Thread Rick McGuire 
Up through 3.2, rxapi used shared memory for interprocess communications
with no user isolation at all. With 4.0, this was changed to the current
setup using sockets and user-level isolation.

There's no real work around for this and there's no plan to support cross
user communications in the future. If anything, if Moritz gets his named
pipe solution working, the isolation will be even tighter with an instance
of rxapi for each ooRexx user.

Rick

On Thu, Jul 26, 2018 at 12:09 PM Erich Steinböck 
wrote:

> We have an open bug report https://sourceforge.net/p/oorexx/bugs/1321/
>
> It seems that the user is trying to access a named RexxQueue from
> different Windows users: the local user, and a Windows Service running
> under the special Windows account LocalService.
>
> Do I correctly understand that today anything that goes through rxapi (and
> as such RexxQueues) is user-specific (on both Windows and Unix)?
>
> The bug report maintains that the issue surfaced when switching from
> ooRexx 3.2 to any later version.  Have rxapi 3.2 functions (like
> RexxQueues) been available across users, and the switch to user-specific
> was done around 4.0?
>
> If so, is there any work-around except making the Windows Service run with
> local user's privileges?
> I assume there were good reasons for this change, and we will not support
> any cross-user rxapi functions in the future.
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Fwd: Address With and variable references in 5.0.0

2018-07-26 Thread Rony G. Flatscher 
On 26.07.2018 14:47, Rick McGuire wrote:
> SVN was giving me fits with the merge, but I believe trunk is now correctly 
> updated with both
> features.
Created installation packages for 32- and 64-bit Windows and a 64-bit version 
for MacOSX for my
students.

For those who are eager to check out the new features over the weekend:
 
(the Dropbox directory
also contains very brief examples in "examples.addressWith" and 
"examples.variableReference" which
are meant for experimentation only).

---rony

P.S.: Please note, the MacOSX version needs Java installed in order to work 
(e.g. from
http://java.com). Standalone MacOSX ooRexx versions should be expected in the 
future (cf. P.O.'s
work in this corner).



>
> On Sat, Jul 21, 2018 at 3:43 PM Rick McGuire  > wrote:
>
> Not of a lot of discussion on this, but also not a lot of objection 
> either. If nothing
> changes, then I will start merging these features back into trunk on 
> Monday.
>
> Rick
>
> On Thu, Jul 19, 2018 at 6:30 AM Rony G. Flatscher  > wrote:
>
> Forwarding to this list as Gil seems to not be able to post currently.
>
> ---rony
>
>
>
>  Forwarded Message 
> Subject:  Re: [Oorexx-devel] Address With and variable references 
> in 5.0.0
> Date: Wed, 18 Jul 2018 14:06:30 -0400
> From: Gil Barmwater  
> 
> To:   Rony G. Flatscher  
> 
>
>
>
> While I agree that merging the two sandboxes into trunk would 
> probably give them more
> exposure, assuming beta builds are available, the "stumbling block" 
> remains the
> documentation.  I have looked at the reference material for Address 
> With for Regina and it
> is extensive.  Other than Rick and Erich, I know of no one who has 
> the capability to
> create that documentation.  While I am willing to help, the DocBook 
> learning curve is
> non-trivial, to say nothing of the requirements for actually building 
> a document.  I would
> definitely not want the code merged into trunk without the 
> documentation being available. 
> So we must wait for Erich to return from vacation it appears.
>
> My initial feeling was we should release 5.0.0 as it now exists in 
> trunk and then do a
> 5.1.0 with the new features - Address With and variableReference - 
> after the documentation
> and testing are finished.  Unfortunately, this approach also requires 
> Erich's time which
> has been limited recently.  So I now think we should get the 
> documentation done as
> described above, allow for some more beta testing of those features 
> and then, finally
> release 5.0.0.
>
> Just my two cents worth... 
>
> Gil B.
>
> PS I have sent this off-list as I am still unable to post to the list 
> - my IP address has
> been flagged for sending spam.  Please feel free to post this to the 
> list for me.  Thanks.
>
> On 7/18/2018 11:25 AM, Rony G. Flatscher wrote:
>> Adding both, addressWith and variableReference to trunk would help 
>> expose it to a much
>> wider audience for experimenting with it once new betas got created 
>> from trunk. Both
>> features are a real boon for ooRexx, IMHO.
>>
>> ---rony
>>
>>
>> On 18.07.2018 12:35, Erich Steinböck wrote:
>>> I'd really value this addition. With RFE#4 it's almost the oldest 
>>> request for
>>> enhancement that we have in our tracker. 
>>>
>>> I'll start doing the required changes for rexxref and rexxpg when 
>>> returning from
>>> vacation.  Finishing will take some time as there are quite a few 
>>> API changes.
>>>
>>> Rick McGuire mailto:object.r...@gmail.com>> 
>>> schrieb am Di., 17.
>>> Juli 2018 22:08:
>>>
>>> I'm not sensing that there is much interest in these features 
>>> being in 5.0.
>>>
>>> Rick
>>>
>>> On Mon, Jul 9, 2018 at 4:12 PM Rick McGuire 
>>> >> > wrote:
>>>
>>> Things have been very quiet about these new features, so I 
>>> don't really know if
>>> anybody is actually playing around with them or not. The 
>>> code is done, tests are
>>> written. The biggest outstanding item is getting the docs 
>>> written. So, we need
>>> to reach a consensus on whether either of these features 
>>> should be in 5.0.0 so
>>> the process of merging can start.
>>>
>>> Rick 
>>>

--
Check out the vibrant tech community on one of the world's most
engaging tech sites,

[Oorexx-devel] RexxQueue user-specific on Windows

2018-07-26 Thread Erich Steinböck 
We have an open bug report https://sourceforge.net/p/oorexx/bugs/1321/

It seems that the user is trying to access a named RexxQueue from different
Windows users: the local user, and a Windows Service running under the
special Windows account LocalService.

Do I correctly understand that today anything that goes through rxapi (and
as such RexxQueues) is user-specific (on both Windows and Unix)?

The bug report maintains that the issue surfaced when switching from ooRexx
3.2 to any later version.  Have rxapi 3.2 functions (like RexxQueues) been
available across users, and the switch to user-specific was done around 4.0?

If so, is there any work-around except making the Windows Service run with
local user's privileges?
I assume there were good reasons for this change, and we will not support
any cross-user rxapi functions in the future.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Fwd: Address With and variable references in 5.0.0

2018-07-26 Thread Rick McGuire 
SVN was giving me fits with the merge, but I believe trunk is now correctly
updated with both features.

Rick

On Sat, Jul 21, 2018 at 3:43 PM Rick McGuire  wrote:

> Not of a lot of discussion on this, but also not a lot of objection
> either. If nothing changes, then I will start merging these features back
> into trunk on Monday.
>
> Rick
>
> On Thu, Jul 19, 2018 at 6:30 AM Rony G. Flatscher 
> wrote:
>
>> Forwarding to this list as Gil seems to not be able to post currently.
>>
>> ---rony
>>
>>
>>  Forwarded Message 
>> Subject: Re: [Oorexx-devel] Address With and variable references in 5.0.0
>> Date: Wed, 18 Jul 2018 14:06:30 -0400
>> From: Gil Barmwater  
>> To: Rony G. Flatscher  
>>
>> While I agree that merging the two sandboxes into trunk would probably
>> give them more exposure, assuming beta builds are available, the "stumbling
>> block" remains the documentation.  I have looked at the reference material
>> for Address With for Regina and it is extensive.  Other than Rick and
>> Erich, I know of no one who has the capability to create that
>> documentation.  While I am willing to help, the DocBook learning curve is
>> non-trivial, to say nothing of the requirements for actually building a
>> document.  I would definitely not want the code merged into trunk without
>> the documentation being available.  So we must wait for Erich to return
>> from vacation it appears.
>>
>> My initial feeling was we should release 5.0.0 as it now exists in trunk
>> and then do a 5.1.0 with the new features - Address With and
>> variableReference - after the documentation and testing are finished.
>> Unfortunately, this approach also requires Erich's time which has been
>> limited recently.  So I now think we should get the documentation done as
>> described above, allow for some more beta testing of those features and
>> then, finally release 5.0.0.
>>
>> Just my two cents worth...
>> Gil B.
>>
>> PS I have sent this off-list as I am still unable to post to the list -
>> my IP address has been flagged for sending spam.  Please feel free to post
>> this to the list for me.  Thanks.
>>
>> On 7/18/2018 11:25 AM, Rony G. Flatscher wrote:
>>
>> Adding both, addressWith and variableReference to trunk would help expose
>> it to a much wider audience for experimenting with it once new betas got
>> created from trunk. Both features are a real boon for ooRexx, IMHO.
>>
>> ---rony
>>
>>
>> On 18.07.2018 12:35, Erich Steinböck wrote:
>>
>> I'd really value this addition. With RFE#4 it's almost the oldest request
>> for enhancement that we have in our tracker.
>>
>> I'll start doing the required changes for rexxref and rexxpg when
>> returning from vacation.  Finishing will take some time as there are quite
>> a few API changes.
>>
>> Rick McGuire  schrieb am Di., 17. Juli 2018 22:08:
>>
>>> I'm not sensing that there is much interest in these features being in
>>> 5.0.
>>>
>>> Rick
>>>
>>> On Mon, Jul 9, 2018 at 4:12 PM Rick McGuire 
>>> wrote:
>>>
 Things have been very quiet about these new features, so I don't really
 know if anybody is actually playing around with them or not. The code is
 done, tests are written. The biggest outstanding item is getting the docs
 written. So, we need to reach a consensus on whether either of these
 features should be in 5.0.0 so the process of merging can start.

 Rick

>>>
>>
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel