search

hellozedan / node-xmpp-bosh

Automatically exported from code.google.com/p/node-xmpp-bosh
0 stars 0 forks source link

Usage from Gajim? #1

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The project page mentions some clients you have tested it with, however they 
seem like programatic clients, however i am looking to use a chat client with 
BOSH support, such as Gajim;

When I tried Gajim I got the following messages however,  (The other 
possibility is that I have misunderstood how BOSH etc is meant to be used and I 
am wiring together incompatible things!)

This one seems to be related to calling toString on a null in some logging 
statements;

DEBUG Tue May 03 2011 22:07:33 GMT+0100 (BST) BOSH::Someone connected
DEBUG Tue May 03 2011 22:07:33 GMT+0100 (BST) BOSH::Processing request: <body 
xmlns="http://jabber.org/protocol/httpbind" 
newkey="e6b9e9d4c7cf615427522e458523a9c06c4ce91e" ver="1.6" ack="1" 
route="talk3.l.google.com:5222" xmlns:xmpp="urn:xmpp:xbosh" wait="30" 
content="text/xml; charset=utf-8" to="gmail.com" xml:lang="en" 
rid="617354065771609" hold="1" xmpp:version="1.0"/>
DEBUG Tue May 03 2011 22:07:33 GMT+0100 (BST) BOSH::Session creation
DEBUG Tue May 03 2011 22:07:33 GMT+0100 (BST) 
BOSH::8AE55735-BE57-48DF-BE30-DE4CB51A26E5::adding a response object. Holding 0 
response objects
DEBUG Tue May 03 2011 22:07:33 GMT+0100 (BST) BOSH::route_parse: DUTIL::args: [ 
'DEBUG',
  Tue, 03 May 2011 21:07:33 GMT,
  'BOSH::route_parse:',
  null ]
DUTIL::arg: null
DUTIL::log_it:astr.length: 0
DUTIL::log_it:Exception:
 TypeError: Cannot call method 'toString' of null
    at /usr/local/lib/node_modules/node-xmpp-bosh/src/dutil.js:96:16
    at Array.forEach (native)
    at log_it (/usr/local/lib/node_modules/node-xmpp-bosh/src/dutil.js:91:8)
    at route_parse (/usr/local/lib/node_modules/node-xmpp-bosh/src/bosh.js:347:3)
    at stream_add (/usr/local/lib/node_modules/node-xmpp-bosh/src/bosh.js:452:19)
    at _handle_incoming_request (/usr/local/lib/node_modules/node-xmpp-bosh/src/bosh.js:1170:13)
    at _on_data_end (/usr/local/lib/node_modules/node-xmpp-bosh/src/bosh.js:1521:3)
    at /usr/local/lib/node_modules/node-xmpp-bosh/src/bosh.js:1570:5
    at /usr/local/lib/node_modules/node-xmpp-bosh/node_modules/underscore/underscore.js:485:26
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/node-xmpp-bosh/src/bosh.js:1607:4)

I changed the log level to INFO to see what would happen, but i got a different 
message.

 GMT+0100 (BST) XMPP PROXY::CLOSE event triggered on XMPPProxy:had_error: false

Original issue reported on code.google.com by simoje...@gmail.com on 3 May 2011 at 9:21

GoogleCodeExporter commented 8 years ago 
Commit #193 should fix this for you. Do let me know if you run into trouble 
with it.

Original comment by dhruvb...@gmail.com on 13 May 2011 at 7:40

GoogleCodeExporter commented 8 years ago 
Closing. Re-open if not fixed.

Original comment by dhruvb...@gmail.com on 13 May 2011 at 7:58

GoogleCodeExporter commented 8 years ago 
I also noticed an error in the route attribute that Gajim is passing.

route="talk3.l.google.com:5222"

Should be:

route="xmpp:talk3.l.google.com:5222"

Maybe you could report it on the Gajim list?

Original comment by dhruvb...@gmail.com on 14 May 2011 at 8:33

GoogleCodeExporter commented 8 years ago 
The reason you got a different message with logging=INFO and logging=DEBUG is 
because the bug was in the code that printed the DEBUG log statements. Also, 
since the 'route' attribute is invalid, the BOSH proxy would revert to SRV 
lookup.

Original comment by dhruvb...@gmail.com on 14 May 2011 at 8:37

GoogleCodeExporter commented 8 years ago 
hi,

yes im not sure Gajim BOSH works very well.

In the meantime I have managed to get punjab and psi working.

I may try psi with node-xmpp-bosh when i get a chance.

Original comment by simoje...@gmail.com on 14 May 2011 at 8:45

GoogleCodeExporter commented 8 years ago 
How did you configure PSI to work with BOSH? I have been trying to get that to 
work myself! Can't find an such option in PSI to enter the BOSH connection 
manager URL.

Original comment by dhruvb...@gmail.com on 14 May 2011 at 9:15

GoogleCodeExporter commented 8 years ago 
shit sorry, i mean pidgin, i keep getting the 2 mixed up.

sorry

simon

Original comment by simoje...@gmail.com on 14 May 2011 at 11:00

GoogleCodeExporter commented 8 years ago 
ah! got you!
unfortunately, node-xmpp-bosh won't work with libpurple because of a bug in the 
BOSH handling by libpurple. I could make it work around that bug, but it would 
make it dead slow for the case for which it was built, namely, multiple streams.

Original comment by dhruvb...@gmail.com on 14 May 2011 at 11:04

GoogleCodeExporter commented 8 years ago 
I've filed a ticket. In case you want to follow it, here's the link: 
http://developer.pidgin.im/ticket/14070

Original comment by dhruvb...@gmail.com on 14 May 2011 at 11:17