On Wed, Sep 29, 2010 at 12:46 PM, Lennard de Rijk <[email protected]> wrote: > Yeah, apparently the ports have changed as well. Which is interesting since > the connection was made successfully, albeit on the wrong port. Fix is on > its way[0]. > Greetings, > Lennard > [0] http://codereview.waveprotocol.org/159001/show
Applied the patch, and probey works like a charm. Echoey connects, and is now a bit more verbose in it's output, but still doesn't seem to work the way I would have expected it to (No output in a wavelet, seems to lock up the console client...?). Unfortunately don't have time to play with wave at the moment, but thanks again for your help thus far. :) ~Justin -- 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.
