Disable WebSockets?

[Bruno Michel]

Hello,

I'm using Faye on one project behind nginx. And so, the WebSocket
can't be used as nginx doesn't support them for the moment. I'd like
to disable the WebSocket transport to avoid the error message in
firebug. Is it possible?

After reading the docs, it doesn't seem to be the case. Should I
propose a patch to add an option on the creation of Faye.Client to
specify which transports to use? Or just one to disable WebSockets?

++
Bruno

[James Coglan]

An API to limit which transports to use might be useful, although we'll need to do it very carefully since some transports are 'special' -- a client can assume the server supports them in order to make the initial handshake and discover the server's other supported transports.

If you want to disable WebSockets for now, you can patch the transport like this:

Faye.Transport.WebSocket.isUsable = function(_,c) { c(false) }

[EyePulp]

I get this in FF6 very reliably - this workaround to shut off
websockets did just the trick. Thanks!

On Aug 30, 6:07 am, James Coglan <jcog...@gmail.com> wrote:

[Bruno Michel]

Thanks for the workaround.

I'll see if I understand the transports selection and the 'special'
ones and, if so, I'll try to submit a patch.

++
Bruno

[upisdown]

Where do we put this? in faye.ru ?

I used to use client.disable("websocket"); 

on the client side but it doesnt seem to be working anymore.

[James Coglan]

On 8 February 2013 00:16, upisdown <trim...@gmail.com> wrote:

I used to use client.disable("websocket"); 

on the client side but it doesnt seem to be working anymore.

This is currently broken but will be fixed in 0.8.9. The original workaround of patching isUsable() should work until then. 

[upisdown]

Okay so I'm not going crazy. But I was forced to learn how to setup HAproxy
so all for the best.

I apologize if I seem dense but where do I apply the patch? I tried putting
the line below in my faye.ru but it threw and error.

Faye.Transport.WebSocket.**isUsable = function(_,c) { c(false) }

[James Coglan]

On 8 February 2013 05:21, upisdown <trim...@gmail.com> wrote:

I apologize if I seem dense but where do I apply the patch? I tried putting
the line below in my faye.ru but it threw and error.

Faye.Transport.WebSocket.isUsable = function(_,c) { c(false) }

This goes in your JavaScript. 

[upisdown]

Any leads on why I would get this error after adding the before mentioned line after the below line in my javascript? 

var faye = new Faye.Client('https://i.hoped.so/faye');

Faye.Transport.WebSocket.isUsable = function(_,c) { c(false) };

1. Uncaught TypeError: string is not a function i.hoped.so:82
1. Faye.Transport.WebSocket.isUsablei.hoped.so:82
2. (anonymous function)faye.js:1
3. jfaye.js:1
4. lfaye.js:1
5. nfaye.js:1
6. Faye.extend.asyncEachfaye.js:1
7. Faye.Transport.Faye.extend.getfaye.js:1
8. Faye.Client.Faye.Class._Afaye.js:1
9. (anonymous function)faye.js:1
10. (anonymous function)faye.js:1
11. Faye.Extensible.pipeThroughExtensionsfaye.js:1
12. Faye.Client.Faye.Class.receiveMessagefaye.js:1
13. Faye.Transport.Faye.extend.Faye.Class.receivefaye.js:1
14. j.onreadystatechange

[upisdown]

Oh I tried it above too and get the same error.

[James Coglan]

On 8 February 2013 09:51, upisdown <trim...@gmail.com> wrote:

Any leads on why I would get this error after adding the before mentioned line after the below line in my javascript? 

var faye = new Faye.Client('https://i.hoped.so/faye');

Faye.Transport.WebSocket.isUsable = function(_,c) { c(false) };

Oh, it takes an additional param these days:

Faye.Transport.WebSocket.isUsable = function($, _, c) { c(false) };