SockJs vs Atmosphere

[Tlvenn]

Hi Tim,

I am wondering if you could share some light over the rational of picking up SockJs and coding the server counter part in java rather than using Atmosphere ?

It seems to me that atmosphere would fit perfectly with vertx...

It integrates with netty and hazelcast out of the box, has a js client and a lot of stuff can be done on the server part within the very neat API it provides.

It just seems that coming from the JVM world, it would be more logical than SockJs...

- Chris

[Tim Fox]

SockJS is a lot more than websockets.

The most important thing about SockJS is that it provides a *websocket-like abstraction* even if websocket connections are not possible (e.g. a corporate proxy/firewall or browser does not allow it).

It falls back to using other transports automatically in this case. I'm only aware of two technologies - sock.js and socket.io that currently does this.

Pure websocket solutions currently have issues in the "real-world".

[Tlvenn]

I realize that and I believe Atmosphere provides the same abstraction within its js client

> https://github.com/Atmosphere/atmosphere/wiki/jQuery.atmosphere.js-API

[Tim Fox]

Also, bear in mind atmosphere is pretty new to the game (1.0 is only a
beta), and when we started SockJS was more mature.

SockJS works very well for us and seems to be a more popular project. I
can't see any reason to change right now.

> --
> You received this message because you are subscribed to the Google
> Groups "vert.x" group.
> To view this discussion on the web, visit
> https://groups.google.com/d/msg/vertx/-/2q58ysaiOyMJ.
> To post to this group, send an email to ve...@googlegroups.com.
> To unsubscribe from this group, send email to
> vertx+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/vertx?hl=en-GB.


--
Tim Fox

Vert.x - effortless polyglot asynchronous application development
http://vertx.io
twitter:@timfox

[Tlvenn]

Well to their defense, they have been pretty conservative with their version numbers, Atmosphere has been stable and I believe used in many place in production for quite some time now.

Dont get me wrong, SockJs works pretty well indeed and I wasnt trying to push for a switch or anything.

I was more curious as the background behind using it against a pure Java project.

[Bruno Santos]

I've used Atmosphere before and it is pretty good framework. Plus, it integrates pretty well with Netty which I believe Vert.X IO is based on. 

Unfortunately I do not have much on hands with SockJS. 

Great subject for a blog post...

Maybe Atmosphere it could be integrated has a Vert.X IO module.

.

[Tim Fox]

My philosophy - "If it ain't broke - don't fix it"

[Wilson MacGyver]

couldn't agree more, especially for a young project with limited
resource, namely ONE :)

> --
> You received this message because you are subscribed to the Google Groups
> "vert.x" group.
> To view this discussion on the web, visit

> https://groups.google.com/d/msg/vertx/-/ONW_9dfPj9cJ.

>
> To post to this group, send an email to ve...@googlegroups.com.
> To unsubscribe from this group, send email to
> vertx+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/vertx?hl=en-GB.



--

Omnem crede diem tibi diluxisse supremum.