Comment #4 on issue 49 by kevincantu: fixed discovery of remote wave service JIDs http://code.google.com/p/wave-protocol/issues/detail?id=49
These symptoms reappear with some certificate problems. As is described here (http://groups.google.com/group/wave- protocol/browse_thread/thread/dccfcd4a2f9ee224), if you run pubsub and conference services on Openfire, and do not have certificates for those, this symptom reappears. A disco#info is requested for the firsts JID (e.g., conference) and then the second JID is never queried for disco#info. Is it possible that the queue for testing every JID, one after the other, is something of a premature optimization? I haven't looked at the other code behind this current failure yet, but will if I have time... -- 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 -~----------~----~----~----~------~----~------~--~---
