In 1.1.1, when I used code like:
dojox.cometd.init("cometd")
the client to not send long-polling-json-encoded as a supportedConnectionType, but now with 1.2.0 it does.
This is confusing my server implementation (WebLogic Server 10.3) as I get a handshake message back.
"successful": false,
"error":
"402:long-polling-json-encoded:Invalid supportedConnectionTypes attribute."
I believe that the server should be able to handle/ignore this new type, but is there a way in the init() that I can set properties that tell the client not to send that supportedConnectionType or should I edit one of the Dojo files somewhere that turns that off that new type until the server-side gets updated to handle it?
try something like: var
try something like:
var comet = dojox.cometd.init(this.cometdURL, { connectionType: "callback-polling" });
i think the connectionType property can be one of the following: "callback-polling", "long-polling" or "long-polling-json-encoded"
solved with unregister
your suggestion put me on the right track. i couldn't get that to work, but after digging around in the source, i found something else that worked after seeing that the connectionTypes are stored in an AdapterRegistry.
http://api.dojotoolkit.org/jsdoc/dojo/1.2/dojo.AdapterRegistry
here is my updated invocation code that removed the undesirable supportedConnectionType in the meta handshake.
dojox.cometd.connectionTypes.unregister("long-polling-json-encoded");
dojox.cometd.init("cometd");
after i made this change now the handshake message looks like this:
message=[{"version":"1.0","minimumVersion":"0.9","channel":"/meta /handshake","id":"0","supportedConnectionTypes":["long-polling","callback-polling "]}]
thanks!