On Sat, 2009-11-14 at 21:15 +1100, Brett Morgan wrote: > I suspect there is an expectation, in both the protocol design, and > the wave sandbox that waves are persistent. We probably should hack a > persistence layer into fed one at some point. In my stupidly large > amount of spare time. ;-)
Yeah, I'm guessing so, however I think that at this point an expectation of persistence is probably not a super good idea. Anyway, yeah persistence is something I'm looking at. The other thing is I think I've found a bug in the FedOne implementation of the federation protocol. Essentially what happens is this: - A wave is created on my fedone server, I add my wavesandbox account and spend a merry two or three minutes talking to myself. - Soon afterwards I have to restart the FedOne server. - I then try and add something to the old wave on the sandbox - The FedOne server recieves the submit packet and then throws an error in the logs however it doesn't return the submit response packet with an error message. This confuses the sandbox which continually resends the submit packet hoping for a response. -- James Purser Collaborynth http://collaborynth.com.au Mob: +61 406 576 553 Skype: purserj1977 Twitter: http://twitter.com/purserj --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
