You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Peter Firmstone (JIRA)" <ji...@apache.org> on 2010/01/06 00:47:54 UTC

[jira] Commented: (RIVER-278) Unicast discovery protocol needs support for HTTP(S)

    [ https://issues.apache.org/jira/browse/RIVER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796923#action_12796923 ] 

Peter Firmstone commented on RIVER-278:
---------------------------------------

The link above has moved to:

http://www.marbro.org/research/discovery.html

> Unicast discovery protocol needs support for HTTP(S)
> ----------------------------------------------------
>
>                 Key: RIVER-278
>                 URL: https://issues.apache.org/jira/browse/RIVER-278
>             Project: River
>          Issue Type: Sub-task
>    Affects Versions: jtsk_2.1
>            Reporter: Mark Brouwer
>
> The unicast discovery protocol is a 'raw' socket protocol that does not support HTTP(S) and does not allow for routing information. To be able to obtain a lookup service proxy in an environment where HTTP(S) and proxy servers are the only possible/allowed way of communication the unicast discovery protocol needs to be extended to allow for HTTP and probably HTTPS as well.
> A modified specification for [DJ.2.6 The Unicast Discovery Protocol|http://www.cheiron.org/research/discovery.html] has been written, modifications compared to the official specification are in blue. A partial implementation to validate these modifications has been done as part of the Cheiron project.
> This issue only represents the modified specification, consequences for Reggie and the implementation classes should  probably be tracked as an independent subtask of RIVER-277.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.