Full duplex communication?

Rahul Somasunderam

unread,

Apr 4, 2012, 3:27:37 PM4/4/12

to asyncht...@googlegroups.com, atmosphere...@googlegroups.com

Hi,

I'm having a server running atmosphere inside of grails on tomcat 7. My client is not a browser, but a java based client built with AHC.

I've been successful in implementing this model:

Server starts up.

Client starts up.

<-- Client connects to server.

--> Server receives message somehow that needs to be sent to client.

Server sends message to client -->

Client receives message

Client creates response

<-- Client sends response over a new connection.

This works beautifully. I've now got a new scenario to address:

Server starts up.

Client starts up.

<-- Client connects to server.

--> Server receives message somehow that needs to be sent to client.

Server sends message to client -->

Client receives message

Client creates response

<-- Client sends response over same connection.

<-- Server responds to the source of the message synchronously

Changes are in bold.

Has anyone implemented something like this? Is it possible?

TIA.

R,

rahul

Jeanfrancois Arcand

unread,

Apr 4, 2012, 3:39:07 PM4/4/12

to asyncht...@googlegroups.com

Salut,

yes, that will works with WebSocket for sure (open a single connection, duplex call on it). It can work as well using HTTP + keep-alive (but you have to make sure your HTTP client/Javascript re-use the same connection for the client second request) => for sure that will works with long-polling. For http-streaming I don't think you can re-use the same connection.

Which client are you using?

A+

-- Jeanfrancois

TIA.

R,

rahul
--
You received this message because you are subscribed to the Google Groups "asynchttpclient" group.
To post to this group, send email to asyncht...@googlegroups.com.
To unsubscribe from this group, send email to asynchttpclie...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/asynchttpclient?hl=en.

Jeanfrancois Arcand

unread,

Apr 4, 2012, 3:42:48 PM4/4/12

to asyncht...@googlegroups.com, atmosphere...@googlegroups.com

Just realized you cross posted to Atmosphere and AHC :-) ... so I know the client you are using.

The answer is yes, it will be easy with AHC to re-use the same connection. Just set the number of connection to a host to 1 so you are guarantee to re-use the connection.

A+

-- Jeanfrancois

Rahul Somasunderam

unread,

Apr 4, 2012, 4:00:10 PM4/4/12

to asyncht...@googlegroups.com, atmosphere...@googlegroups.com

Hi Jeanfrançois,

I'm using your AsyncHttpClient library with a custom handler that implements AsyncHandler<String>. Would I have to rewrite it to use Websockets?

I believe the server component will automcatically support WebSockets since it uses Atmosphere.

R,

rahul

Jeanfrancois Arcand

unread,

Apr 4, 2012, 4:09:07 PM4/4/12

to asyncht...@googlegroups.com, Rahul Somasunderam, atmosphere...@googlegroups.com

Salut,

On 12-04-04 4:00 PM, Rahul Somasunderam wrote:

Hi Jeanfrançois,

I'm using your AsyncHttpClient library with a custom handler that implements AsyncHandler<String>. Would I have to rewrite it to use Websockets?

I believe the server component will automcatically support WebSockets since it uses Atmosphere.

With AHC you will need to switch handler...I'm working on an Atmosphere Java Client for the upcoming 1.0.0 release that will hides that and will negotiate with the Atmosphere server which transport is the best/optimal....but first I need to release Atmosphere 0.9 before I start working on that :-) So long answer to say that you will need to do some AHC work ... Tomcat 7 doesn't yet support Websocket so you may have to be force to use HTTP (or 7.0.26 might be, need to check).

A+

-- Jeanfrancois

Rahul Somasunderam

unread,

Apr 4, 2012, 5:47:01 PM4/4/12

to atmosphere...@googlegroups.com, asyncht...@googlegroups.com, Rahul Somasunderam

7.0.26 still doesn't support WebSockets.

http://gurkanerdogdu.blogspot.com/2012/03/websocket-in-tomcat-7-and-tomcat-8.html says it will be supported from 7.0.27+

Thanks!

R,

rahul

R,

rahul

To post to this group, send email to asynchttpclient@googlegroups.com.
To unsubscribe from this group, send email to asynchttpclient+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/asynchttpclient?hl=en.

--
You received this message because you are subscribed to the Google Groups "asynchttpclient" group.

To post to this group, send email to asynchttpclient@googlegroups.com.
To unsubscribe from this group, send email to asynchttpclient+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/asynchttpclient?hl=en.

--
You received this message because you are subscribed to the Google Groups "asynchttpclient" group.

To post to this group, send email to asynchttpclient@googlegroups.com.
To unsubscribe from this group, send email to asynchttpclient+unsubscribe@googlegroups.com.

Rahul Somasunderam

unread,

Apr 5, 2012, 5:03:20 PM4/5/12

to asyncht...@googlegroups.com, atmosphere...@googlegroups.com

Looks like I got lucky. I upgraded my tomcat to 7.0.27. And AHC to 1.7.2.

I'm now getting this exception:

java.lang.IllegalStateException: Invalid upgrade protocol, status should be 101 but was 501

at com.ning.http.client.websocket.WebSocketUpgradeHandler.onStatusReceived(WebSocketUpgradeHandler.java:67)

at com.ning.http.client.providers.netty.NettyAsyncHttpProvider$WebSocketProtocol.handle(NettyAsyncHttpProvider.java:2307)

at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.messageReceived(NettyAsyncHttpProvider.java:1117)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)

at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndFireMessageReceived(ReplayingDecoder.java:522)

at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:501)

at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:438)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)

at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:343)

at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:274)

at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:194)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:680)

Caught: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Invalid upgrade protocol, status should be 101 but was 501

java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Invalid upgrade protocol, status should be 101 but was 501

at com.ning.http.client.providers.netty.NettyResponseFuture.abort(NettyResponseFuture.java:297)

at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.abort(NettyAsyncHttpProvider.java:1315)

at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.exceptionCaught(NettyAsyncHttpProvider.java:1531)

at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:117)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:558)

at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:777)

at org.jboss.netty.handler.codec.replay.ReplayingDecoder.exceptionCaught(ReplayingDecoder.java:456)

at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:117)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:558)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:553)

at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:426)

at org.jboss.netty.channel.AbstractChannelSink.exceptionCaught(AbstractChannelSink.java:47)

at org.jboss.netty.channel.DefaultChannelPipeline.notifyHandlerException(DefaultChannelPipeline.java:645)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)

at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:777)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)

at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndFireMessageReceived(ReplayingDecoder.java:522)

at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:501)

at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:438)

at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:558)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:553)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)

at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:343)

at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:274)

at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:194)

at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102)

at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)

Caused by: java.lang.IllegalStateException: Invalid upgrade protocol, status should be 101 but was 501