I think we should remove discovery V1 from the specification.
Also because V2 has a provider negotiation mechanism and each provider
has a unique discovery id, it's possible to support multiple languages
here with different providers. While the standard provider uses
MarshalledInstance to contain the registrar proxy serialized bytes, in
the new providers I've created in JGDMS, I just use serialized bytes
with AtomicMarshalOutputStream and AtomicMarshalInputStream. So other
languages or protocols can be used to store the registrar proxy in
serialized from.
On 15/02/2018 12:14 PM, Gerard Fulton (JIRA) wrote:
Gerard Fulton created RIVER-452:
-----------------------------------
Summary: Jini Discovery and Join Specification
Key: RIVER-452
URL: https://issues.apache.org/jira/browse/RIVER-452
Project: River
Issue Type: Story
Reporter: Gerard Fulton
Remove references to Java in the Jini Discovery and Join Specification
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
