You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Protocol seems to mostly be "done" but is still up for modifications based on credible, objective feedback with use cases or performance considerations
Experience implementing or productizing implementations can still cause modifications
The Java implementation is mostly functional. It is not yet production worthy. We have implemented it alongside the definition of the protocol and the protocol has evolved while doing so.
We do not yet have a TCK but would like to.
We would like to have an implementation in Javascript (and/or C) and show interop amongst them before we consider the protocol ready to call v1.0
The text was updated successfully, but these errors were encountered:
@benjchristensen regarding the JavaScript (browser/server) implementations, is there anyone working on those actively (right now I only see two empty repos)? I am interested in contributing and would like to avoid duplicating efforts.
@pk11 I am currently working on getting the JS version to a state of being able to run tests. Please feel free to help in anyway. If you would like to coordinate feel free to reach out to me via email or twitter
Pinging folks from the Reactive Streams community to express interest in your feedback (and involvement if you like what you see).
@viktorklang @rkuhn @ktoso @drewhk @jbrisbin @maniksurtani @danarmak @pk11 @smaldini @alkemist @purplefox @mariusae @normanmaurer
Related to discussions in reactive-streams/reactive-streams-io#1 and reactive-streams/reactive-streams-io#8
Relevant documents for review include:
Status:
The text was updated successfully, but these errors were encountered: