[
https://issues.apache.org/jira/browse/RIVER-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368735#comment-16368735
]
Gerard Fulton commented on RIVER-452:
-------------------------------------
Peter [email protected] via river.apache.org
12:43 PM (4 hours ago)
to commits
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.
> 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
> Priority: Minor
>
> Remove implementation details from the [Jini Discovery and Join
> Specification|https://river.apache.org/release-doc/current/specs/html/discovery-spec.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
