Move to using websockets from long-polling about apollo

[nathandunn]

So, using the grails-websocket would be by far the easiest as it wraps both Spring and Stomp and would result in most likely a lot less code:

https://github.com/zyro23/grails-spring-websocket

However, since everything is so dojo-fied . . it might be very problematic. If I re-enable the service via the service endpoint (AnnotationEditorEndpoint) it might work well enough.

[nathandunn]

The AMD is the bigger problem . . . even if I get the older code in there, adding the annotation to the controllers, means that I still need access to the grails service classes. I can do this via websockets . . . or somehow include HTML that will bridge the two implementations. Its unfortunate that dojo does not support stomp.

[cmdcolin]

we use a couple non-AMD modules in webapollo. it's a little hacky but i have examples of this setup at the top of main.js to load some bbop modules.

[nathandunn]

Awesome. I see. That looks pretty straight-forward. Doing this with spring and stomp library support eliminates a lot of code.

I also wanted to note that websockets are very well supported on all major web browsers except IE 8 and 9.

Nathan

On Jan 2, 2015, at 1:19 PM, Colin Diesh [email protected] wrote:

we use a couple non-AMD modules in webapollo. it's a little hacky but i have examples of this setup at the top of main.js to load some bbop modules.

—
Reply to this email directly or view it on GitHub #44 (comment).

[cmdcolin]

ie8 and 9 are not really supported by jbrowse either. from the homepage

Microsoft Internet Explorer (9 and later, 10 required for BAM, BigWig, VCF+Tabix)

[nathandunn]

That worked great . . . in here . . . now trying to put it all back together . . on this branch (grails1-realdata) until after the conference.

https://trello.com/c/drb7Fzk4

[nathandunn]

Note that I also added a "./copy_client.sh" method for the inteirm.

[cmdcolin]

why is sockjs needed? it says it is websocket emulation

[nathandunn]

The most important reason to use it is because it integrates directly with Spring and thus Grails.

SockJS, from this description:

https://github.com/sockjs/sockjs-client https://github.com/sockjs/sockjs-client

tries to use native web sockets first and then uses the fallback. This is nice, but definitely not essential.

I think the other reason is that its a nice wrapper around web sockets, as well (on both ends) and requires a lot less (and more manageable code).

Nathan

On Jan 2, 2015, at 2:47 PM, Colin Diesh [email protected] wrote:

why is sockjs needed? it says it is websocket emulation

—
Reply to this email directly or view it on GitHub #44 (comment).

[cmdcolin]

sockjs has an extra protocol layer built on top of websockets. i would personally vote against it since we already established we don't need the additional backwards compatibility.

[cmdcolin]

i dunno. i guess things like socket.io also have an extra protocol. it just seems like it is kind of a silly thing to have but i won't protest

[nathandunn]

Convenience wrappers are good things. Especially if they implement a lot of sane defaults that provide stability, performance, and scalability.

Nathan

On Jan 2, 2015, at 3:26 PM, Colin Diesh [email protected] wrote:

i dunno. i guess things like socket.io also have an extra protocol. it just seems like it is kind of a silly thing to have but i won't protest

—
Reply to this email directly or view it on GitHub #44 (comment).

[nathandunn]

hell's yes!