> On 26 Sep 2018, at 02:41, James Roper wrote:
>
> Sounds good to me, I'll ping Viktor to make sure he sees it too.
The "Synchronization primitives in Reactive Streams implementations" thread on
concurrency-interest mailing list:
http://cs.oswego.edu/pipermail/concurrency-interest/2018-S
Sounds good to me, I'll ping Viktor to make sure he sees it too.
On Wed, 26 Sep 2018 at 06:34, Pavel Rappo wrote:
>
> > On 25 Sep 2018, at 05:33, James Roper wrote:
> >
> > Hi Pavel,
> >
> >
> >
> > As for the MutexExecutor itself, that was mostly written by Viktor
> Klang, and I believe he wr
> On 25 Sep 2018, at 05:33, James Roper wrote:
>
> Hi Pavel,
>
>
>
> As for the MutexExecutor itself, that was mostly written by Viktor Klang, and
> I believe he wrote it based on his experience implementing similar constructs
> for Akka mailboxes. There is one major problem with it that I
Hi Pavel,
MicroProfile doesn't do implementations, or even have a concept of a
reference implementation, which is why that executor isn't there. It is
however in one of the implementations of the spec that we've created at
Lightbend:
https://github.com/lightbend/microprofile-reactive-streams/blob
Hi James,
It sounds like the project is being very active. Glad to hear that! No matter
how good a mailing list is, in practice, it cannot be the best mailing list for
every topic there is. core-libs-dev is no exception. It's good to see you've
found another way to make progress on the project.
T
Hi Pavel,
Thanks for asking about this. I was meant to send an update to the list
earlier but never got around to it.
As you probably noticed from the history of this thread, there was a
deafening silence in response to it. We decided that core-libs-dev might
not have been the best place to start
Hi James,
What's the status of the project? Has it been abandoned?
-Pavel
> On 22 Mar 2018, at 00:09, James Roper wrote:
>
> Hi all,
>
> We've created a reference implementation. It's been done in such a way that
> implementation of new features (stages) is quite straight forward, there is
>
Hi all,
We've created a reference implementation. It's been done in such a way that
implementation of new features (stages) is quite straight forward, there is
an abstraction that does the hard work of handling concurrency, the
reactive streams spec conformance, and managing demand and buffering,
Hi all,
An update on this. We've now filled out the API with feature parity with
the JDK8 Streams API - for operators that make sense in Reactive Streams.
We've provided example implementations of the API backed by both Akka
Streams and rxjava, showing that it can be widely implemented. The TCK
st
To answer the questions at the bottom: the next step is to start working
on this and get folks excited about contributing. There's plenty of
time for process later, but filing a JEP or creating a project shouldn't
be a barrier to innovating.
On 2/28/2018 10:33 PM, James Roper wrote:
Hi all,
Hi all,
We've put together a simple proposal for this. Please read the README for
an introduction to this proposal.
https://github.com/lightbend/reactive-streams-utils
Regards,
James
On 22 February 2018 at 11:47, James Roper wrote:
> Hi all,
>
> This is an email to give people a heads up tha
11 matches
Mail list logo
