Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 49 by kevincantu: fixed discovery of remote wave service JIDs
http://code.google.com/p/wave-protocol/issues/detail?id=49
> What steps will reproduce the problem?
Connect to a wave server running more than one XMPP service.
If the wave server is not the first JID listed, you will be unable to
connect, because the code in XmppDisco.java is testing them one at a time,
and waiting forever for responses which do not come.
> What is the expected output? What do you see instead?
There should be disco#info requests and responses for more than just the
first item.
> What version of the product are you using? On what operating system?
0bf003ae4aae, on Ubuntu Linux
> Please provide any additional information below.
My patch, which I just submitted via the request_codereview tool, fixes this
issue by causing a disco#info request to be sent for each JID provided by
the XMPP server in the disco#items response.
I also have added several small tweaks to the shell scripts for
compatibility with dash, the 'sh' in Ubuntu, and for my own preferences.
What is most significant, however, are my changes to XmppDisco.java. You
may also want to add more testing beyond the changes I have made to
XmppDiscoTest.java.
I hope this will make new testing easier for people!
-- Kevin Cantu
Attachments:
wave-protocol-kshh-f77326b8f09d.diff 7.8 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---
