Hello Gerard,
Help is always welcomed, the Jini standards are quite old, so yes, I
think it's an area definitely in need of some love. Documentation or
standards that explain the philosophies / design patterns River is based
on, I can see how that adds appeal. I'll certiainly jump in and help
with reviews, there might be others interested in becoming involved as well.
Thanks,
Peter.
On 1/02/2018 12:09 PM, Gerard Fulton wrote:
Hi Guys,
I wanted to float an idea by list that has been in my head for several
years. The idea is to prioritize the modernization of the River
specification into a set of language a d transport agnostic architectural
principles. River currently supports architectural concepts like discovery,
events, proxies and more! In reality, both the implementation language and
communication transport are minor details. For example a discovery service
implementation could backed by DNS and exposed by a WebSockets
communications transport protocol. I my opinion the most important part of
the DNS discovery service example is the application protocol which
potentially could be defined by a request/response model.
As a Java developer, I fear that the wider adoption and growth of River are
being empeeded by our laser like focus on River's Java reference
implementation.
Feedback is a gift!
-Gerard Fulton
