Hi, folks,
(Note: You're receiving this email because you're on the dev@ list for
one or more Apache Software Foundation projects.)
For ApacheCon North America 2019, we asked projects to participate in
the creation of project/topic specific tracks. This was very successful,
with about 15 projects
Although probably not well known, River 3.0's remote method calls are
communicated at native socket speed.
I have considered writing deflate endpoints for JERI, which would
compress and further improve throughput, one case against doing so is,
when compression is used with encryption, there is
Thanks Bryan,
Be good to have a release to address the memory bug (no pun intended).
Even better will be future binary releases based on Modules. Services
built with modules are so much simpler. But so no one gets upset, all
existing build tools, systems and conventions will continue to work
Peter,
Just reviewed the release. My apologies for taking so long to get
this done. It's been a busy time. Thanks for all the effort to pull
this together.
Bryan
On Fri, Jun 16, 2017 at 12:42 AM, Peter wrote:
> Anyone have some cycles to participate in the release vetting process?
>
> River
Anyone have some cycles to participate in the release vetting process?
River 3.0.1 is a bug fix release.
Remember if we're unable to continue this project, then we lose the
ability to maintain River / Jini and we also lose the legal protections
and visibility of Apache.
Apart from modularity
