Atmosphere Jersey api and WebRTC not work well together

[alfonsodomenici]

I have provided two samples of using Atmosphere with Webrtc to establish an audio-video communication between two browser.
The first sample using Atmosphere Handler api works well.
The second sample using Atmosphere Jersey api don't works.

[carloslizarazo]

Hi Alfonso

Where can i find these samples ?
I'm looking for a way to use Atmosphere with RTC ... and it's pretty difficult to find some light in this subject

Thanks for your attention !!!!!!! ...

[alfonsodomenici]

Hi Carlos,

Please send me an email and I'll send you the working sample.

The sample with Atmosphere Jersey API for now does not work.
I hope that Jeanfrancois will able to find time to solve the issue..
I have not been able to solve it.

Alfonso

2013/2/21 carloslizarazo notifications@github.com

Hi Alfonso

Where can i find these samples ?
I'm looking for a way to use Atmosphere with RTC ... and it's pretty
difficult to find some light in this subject

Thanks for your attention !!!!!!! ...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/905#issuecomment-13871233.

[joelbars]

Hi Mr. Alfonso,

It's been a long time since this issue, I have the same question of Carlos, where can I find the samples. I want to see if I can help with the one that doesn't work too (if it was not fixed yet).

Thanks in advance.

[veeramarni]

Mr Alfonso,

Can you please send me the sample as well to my email marni.srikanth@gmail.com? I will look into the issue. Let me know which application server/media server you are using for this.

[jfarcand]

OK with the following really ugly hack, I can make it work

    @POST
    //@Broadcast(writeEntity = false)
    public void publish(@FormParam("message") String message,
            @PathParam("topic") Broadcaster topic) {
        logger.info("Sending message {} to channel {}", new Object[] {
                message, topic.getID() });
        try {
            Thread.sleep(1000);
        } catch (InterruptedException e) {
            e.printStackTrace();
        }
        //return new Broadcastable(message, "", topic);
        topic.broadcast(message);
    }

So it seems there is an issue inside Jersey or the underlying WebSocket that cause the message to be send out of order, causing the application to fail. I will soon add the sample in the workspace, so @veeramarni you can take a look to see if you spot something. Thanks!

[veeramarni]

@jfarcand let me know once you have the sample ready.

[jfarcand]

OK, both samples are here. The AtmosphereHandler works, Jersey is broken unless you add the ugly hack. Any help appreciated. I've tested using 2 machines with FF and Chrome as Opera and Safari aren't supporting web-rtc properly (at least from the script).

[jfarcand]

Won't fix that.