[
https://issues.apache.org/jira/browse/GOSSIP-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052372#comment-16052372
]
Gary Dusbabek commented on GOSSIP-50:
-------------------------------------
I've spent some time looking into options, and we have quite a few.
1. HTTP via Netty. Pro: few other dependencies, Con: A lot of work to set up
handlers and address configure Netty.
2. HTTP via high-level framework (Dropwizard, Vert.x, etc.) Pro: out-of-the-box
HTTP. Con: brings in a lot of dependencies (e.g. Jackson, etc.)
3. Websockets - Still HTTP(ish), but better suited to stateful protocols like
gossip.
I'd like to solicit opinions before moving forward with this. I'm not 100%
convinced HTTP is the right choice as it mixes in transport and protocol, to
which we would add another protocol (say, JSON). Plus, HTTP isn't generally
suited for dialogues between nodes--we'd have to do a fair amount of work to
track messages, acks, etc.
Lastly, looking at our TransportManager interface, I expect there will be some
adjustments.
Anyway, I'm keen to get the discussion going around this and a solid design
that we can start iterating on.
> HTTP as transport
> -----------------
>
> Key: GOSSIP-50
> URL: https://issues.apache.org/jira/browse/GOSSIP-50
> Project: Gossip
> Issue Type: New Feature
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Fix For: 0.1.3
>
>
> It would be great to have an http transport as an alternative to UDP. I think
> the way to go here is convert to a multi-module project and build a WAR. The
> WAR project will run GossipManager (or GossipService) in the application
> context and the passiveGossipThread is converted into an http servlet
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
