Thanks Roy, I'll keep that in mind.
On 16/02/2022 3:15 am, Roy T. Fielding wrote:
On Feb 15, 2022, at 4:05 AM, Peter Firmstone
wrote:
I think the PMC has already decided River's fate, and I tend to agree with
their decision, the problem is that historically, it hasn't been possible to
innov
Some final thoughts on using OSGi with Jini.
https://www.artima.com/weblogs/viewpost.jsp?thread=202304
This was always a contentious issue historically on Jini lists, I expect
there will be vastly differing opinions on the subject, so I haven't
made any decisions that would constrain developer
Hi Michał,
I didn't take it personal, and don't expect you to take it personal
either when I say, I'm pretty sure everyone here is aware of River /
Jini limitations.
Anyway River has been a lot of fun, all the best for the future
everyone, hope to see you around from time to time.
Cheers,
Hi Peter,
> On 16 Feb 2022, at 10:01, Peter Firmstone wrote:
>
> Inline below.
>
> On 16/02/2022 5:24 pm, Michał Kłeczek wrote:
>>
>>> On 16 Feb 2022, at 04:25, Peter Firmstone
>>> wrote:
>>>
>>> From the CodebaseAccessor service.
>>>
>>> The CodebaseAccessor proxy (local code) is passed a
Hi Michał,
Inline below.
On 16/02/2022 5:24 pm, Michał Kłeczek wrote:
On 16 Feb 2022, at 04:25, Peter Firmstone wrote:
From the CodebaseAccessor service.
The CodebaseAccessor proxy (local code) is passed as a parameter along with a
MarshalledInstance of the proxy, by ProxySerializer to P
> On 16 Feb 2022, at 04:25, Peter Firmstone wrote:
>
> From the CodebaseAccessor service.
>
> The CodebaseAccessor proxy (local code) is passed as a parameter along with a
> MarshalledInstance of the proxy, by ProxySerializer to ProxyCodebaseSpi.
>
> https://github.com/pfirmstone/JGDMS/blob/
Hi Michał, responses inline below.
On 15/02/2022 10:22 pm, Michał Kłeczek wrote:
On 15 Feb 2022, at 13:05, Peter Firmstone
wrote:
How the client knows the code needed to deserialise?
The service provides this information, typically in a services
configuration,
How is this configura
> On Feb 15, 2022, at 4:05 AM, Peter Firmstone
> wrote:
>
> I think the PMC has already decided River's fate, and I tend to agree with
> their decision, the problem is that historically, it hasn't been possible to
> innovate inside the Apache River project, innovation has been forced to
> hap
Follow up:
> On 15 Feb 2022, at 13:05, Peter Firmstone wrote:
>
>
>>
>> - How do you provide the above mentioned JavaSpaceEventPublisher
>> - How would you provide a java.sql.DataSource as a service?
>
>
> If you don't have an ObjectEndpoint, then there is no one to authenticate,
> you only
> On 15 Feb 2022, at 13:05, Peter Firmstone wrote:
>
>
>> How the client knows the code needed to deserialise?
> The service provides this information, typically in a services configuration,
>
How is this configuration provided to the client and when?
> by default this is a space separated li
On 15/02/2022 8:29 pm, Michał Kłeczek wrote:
Hi Peter,
JGDMS uses a new implementation of a subset of the Java
Serialization’s stream format, with input validation and defenses
against malicious data (all connections are first authenticated when
using secure endpoints). Codebase annotatio
Hi Peter,
> JGDMS uses a new implementation of a subset of the Java Serialization’s
> stream format, with input validation and defenses against malicious data (all
> connections are first authenticated when using secure endpoints). Codebase
> annotations are no longer appended in serialization
Hi Michał, thank you for your compliment, I can assure you, I have had a
lot of help and guidance from others ;-).
You are right, people have different visions and needs, on github you
can fork and collaborate, or fork and do your own thing. The vision and
the implementation are two different
Hi All,
Based on the excelent work of (mainly) Peter Firmstone (et al) I am personally
working on “River 4.0” right now and was planning to share my work with the
community soon(tm).
1. Implementation of my old idea of making codebase annotations objects
implementing a specific interface (inst
-
*From:* Peter Firmstone
*Sent:* Thursday, February 10, 2022 12:12 AM
*To:* dev@river.apache.org
*Subject:* Re: [DISCUSS] Moving Apache River to the Attic
Even in the Attic, River will remain a valuable resource of information.
When OpenJDK published JEP411 in April 2021, they believed what we were
technology.
Bishnu Prasad Gautam
From: Peter Firmstone
Sent: Thursday, February 10, 2022 12:12 AM
To: dev@river.apache.org
Subject: Re: [DISCUSS] Moving Apache River to the Attic
Even in the Attic, River will remain a valuable resource of information.
When
Even in the Attic, River will remain a valuable resource of information.
When OpenJDK published JEP411 in April 2021, they believed what we were
already doing with River was impossible, which succinctly sums up a
number of River's features.
https://mail.openjdk.java.net/pipermail/security-dev
I agree it is time.
Well said Jeremy! Thanks for sharing.
I have fond memories of Jini conferences in Chicago and Brussels (even if all I
remember is the Delirium Cafe).
Dan Rollo
> On Feb 9, 2022, at 10:03 AM, Jeremy R. Easton-Marks
> wrote:
>
> I, sadly, agree that it is time to move this
I, sadly, agree that it is time to move this project to the Attic. While I
hoped to work on this as a side project, I have not been able to carve out
time for it. While I do think this project has a lot of potential, without
some type of sponsorship in time and resources I don't see it moving
forwa
Concur
On Mon, Feb 7, 2022 at 16:41 Roy T. Fielding wrote:
> Hello everyone,
>
> It's that time of year when I try to figure out what I am doing and
> what I am not, and try to cut back on the stuff that seems unlikely
> to succeed. I suspect the same is true of others.
>
> I had hoped that more
20 matches
Mail list logo
