Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Subject: Re: Enable camel/netty4 to support full duplex (bidirectional)
 asynchronous sockets
References: <1449796009188-5774972.post@n5.nabble.com>
From: Carl Nygard <cjnygard@gmail.com>
Content-Type: text/plain;
	charset=utf-8
In-Reply-To: <1449796009188-5774972.post@n5.nabble.com>
Message-Id: <CADA8B65-0B1A-4D69-B8E7-2B90B21F69D2@gmail.com>
Date: Fri, 11 Dec 2015 16:49:38 -0500
To: "dev@camel.apache.org" <dev@camel.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Can you just write the Java bidirectional component as a standalone front en=
d and let it talk to the two end points in camel?

--carl

> On Dec 10, 2015, at 8:06 PM, chadkelly <chadkellyspam@gmail.com> wrote:
>=20
> Please, can any developers guide me on extending Camel/Netty4 to support f=
ull
> duplex (bidirectional) asynchronous network communication over the exact
> same UDP/TCP port? I need to accomplish this task before XMas with your
> generosity and guidance. The target component is Netty4 for both UDP and
> TCP. If you know of any existing solution that solves this problem, please=

> share, as this issue has much discussion with no published solution. The
> requirements cannot change because existing systems (non-Camel) are alread=
y
> designed to perform asynchronous bidirectional sockets I/O over the single=

> established socket (and session for TCP).
>=20
> Relevant Camel tickets are already documented here:
> https://issues.apache.org/jira/browse/CAMEL-1075
> https://issues.apache.org/jira/browse/CAMEL-2624
>=20
>=20
> Consider the following "invalid" example that attempts to enable a full
> duplex asynchronous Camel route between endpoint1 and endpoint2. It
> important to notice that this design will cause camel to open 1 tcp sessio=
n
> for =E2=80=9Cfrom route1 endpoint1=E2=80=9D and 1 tcp session for =E2=80=9C=
to route2 endpoint1=E2=80=9D
> (i.e. socket bind collision). This violates the one asynchronous
> bidirectional socket requirement.=20
>=20
> <endpoint id=3D"endpoint1"
> uri=3D"netty4:tcp://localhost:7000?sync=3Dfalse&amp;disconnect=3Dfalse..."=
 />
> <endpoint id=3D"endpoint2"
> uri=3D"netty4:tcp://localhost:7001?sync=3Dfalse&amp;disconnect=3Dfalse..."=
 />
> <route id=3D"route1">
>    <from ref=3D"endpoint1" />
>    <to ref=3D"endpoint2" />=20
> </route>
> <route id=3D"route2">
>    <from ref=3D"endpoint2" />
>    <to ref=3D"endpoint1" />=20
> </route>
>=20
> What is the easiest design to enable this requirement? I prefer to use the=

> design of an existing Camel developer, because I am new to Camel. Two
> initial design options are presented below:
>=20
> Option1 is to add optional seda: or direct: component to the NettyConsumer=

> class (if such a thing can be done). For example, endpoint1 and endpoint2
> have a seda: component to enable a producer backchannel.=20
> <endpoint id=3D"endpoint1"
> uri=3D"netty4:tcp://localhost:7000?seda=3DmySeda1&amp;sync=3Dfalse&amp;dis=
connect=3Dfalse..."
> />
> <endpoint id=3D"endpoint2"
> uri=3D"netty4:tcp://localhost:7001?seda=3DmySeda2&amp;sync=3Dfalse&amp;dis=
connect=3Dfalse..."
> />
> <route id=3D"route1">
>    <from ref=3D"endpoint1" />
>    <to uri=3D"seda:mySeda2" />=20
> </route>
> <route id=3D"route2">
>    <from ref=3D"endpoint2" />
>    <to uri=3D"seda:mySeda1" />
> </route>
>=20
> Option2 is to add optional localhost server to the NettyConsumer class (if=

> such a thing can be done). For example, endpoint1 and endpoint2 have a
> localhostServerPort to enable a producer backchannel.
>=20
> <endpoint id=3D"endpoint1"
> uri=3D"netty4:tcp://localhost:7000?localhostServerPort=3D8000&amp;sync=3Df=
alse&amp;disconnect=3Dfalse..."
> />
> <endpoint id=3D"endpoint2"
> uri=3D"netty4:tcp://localhost:7001?localhostServerPort=3D8001&amp;sync=3Df=
alse&amp;disconnect=3Dfalse..."
> />
> <route id=3D"route1">
>    <from ref=3D"endpoint1" />
>    <to
> uri=3D"netty4:tcp://localhost:8001?clientMode=3Dtrue&amp;disconnect=3Dfals=
e&amp;sync=3Dfalse..."
> />=20
> </route>
> <route id=3D"route2">
>    <from ref=3D"endpoint2" />
>    <to
> uri=3D"netty4:tcp://localhost:8000?clientMode=3Dtrue&amp;disconnect=3Dfals=
e&amp;sync=3Dfalse..."
> />
> </route>
>=20
> Does this make sense? I may be typing things that may not make
> implementation sense, so please guide me in coming up with any practical
> solution that will work in Camel.=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> --
> View this message in context: http://camel.465427.n5.nabble.com/Enable-cam=
el-netty4-to-support-full-duplex-bidirectional-asynchronous-sockets-tp577497=
2.html
> Sent from the Camel Development mailing list archive at Nabble.com.