On Mon, Aug 9, 2010 at 5:58 PM, andreas <[email protected]>wrote:
> No open one. I haven't checked the closed ones yet, pretty busy right > now. > > It seems strange to me though that no one else has run into this. Did > anybody try to reproduce this? Did no body open more than one Wave in > FedOne SimpleWebClient? ;-) > > Well, with the websockets working again I'm sure we should be able to reproduce this. However I do suggest that you make an issue for it here [0] so that we can keep better track of things. I'll try and see if I can reproduce it locally if I can find the time for it, just opening a second wave should do? Greetings, Lennard [0] http://code.google.com/p/wave-protocol/issues/entry > On 9 Aug., 09:51, Lennard de Rijk <[email protected]> wrote: > > Is there an open issue on this in our tracker? > > > > Greetings, > > Lennard > > > > On Mon, Aug 9, 2010 at 4:58 PM, andreas <[email protected] > >wrote: > > > > > > > > > Hey Anthony, > > > > > back to the problem with switching between waves. I just gave it a try > > > with the latest WebSocket fix. The problem is still there though. I > > > found the log when the problem occurs (upon reopening a wave): > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- 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.
