Re: deserialization remote invocation strategy

2017-02-15 Thread Peter
message From: Patricia Shanahan <p...@acm.org> Sent: 15/02/2017 09:18:46 pm To: dev@river.apache.org Subject: Re: deserialization remote invocation strategy I still have some contacts into the UCSD computer science department  from when I was doing my PhD. If we had a stated security

Re: deserialization remote invocation strategy

2017-02-15 Thread Peter
to AtomicSerial is available on the jgdms wiki. Regards, Peter. Sent from my Samsung device.     Include original message Original message From: Michał Kłeczek <mic...@kleczek.org> Sent: 15/02/2017 09:07:33 pm To: dev@river.apache.org Subject: Re: deserialization remote invocation st

Re: deserialization remote invocation strategy

2017-02-15 Thread Michał Kłeczek
. Sent from my Samsung device. Include original message Original message From: Michał Kłeczek<mic...@kleczek.org> Sent: 15/02/2017 08:04:39 pm To: dev@river.apache.org Subject: Re: deserialization remote invocation strategy The code actually does what I've described above, but

Re: deserialization remote invocation strategy

2017-02-15 Thread Peter
message Original message From: Michał Kłeczek <mic...@kleczek.org> Sent: 15/02/2017 08:04:39 pm To: dev@river.apache.org Subject: Re: deserialization remote invocation strategy > The code actually does what I've described above, but don't take my word for  >it, check it

Re: deserialization remote invocation strategy

2017-02-15 Thread Michał Kłeczek
The code actually does what I've described above, but don't take my word for it, check it for youself. :) If you disagree, don't use it. It works the other way around - before I decide to use it - I have to understand how it works. Even more so if we are talking about security. That is why