In order to make testing easier and to ensure a common code base, I have created a clone of FedOne and uploaded the mongodb persistence mechanism to that version. It can be found at https://code.google.com/r/awatkins03-mongodb/ . Just create a new folder and clone https://awatkins03-mongodb.googlecode.com/hg/ awatkins03-mongodb
You'll need to copy in your wave cert and run-* scripts. In run- server you'll need to add the flag -- waveserver_enable_persistence=true . Lastly, you need to install mongodb (takes about 5 mins, instructions here: http://www.mongodb.org/display/DOCS/Getting+Started) R, Anthony On Mar 22, 8:20 am, James Purser <[email protected]> wrote: > On Mon, 2010-03-22 at 02:52 -0700, W. Palsgraaf wrote: > > James, > > > Did you come any further with this? > > I have got the same problem. > > Unfortunately not. I haven't tested it against another fedone instance, > so I can't tell if it's something peculiar with the wavesandbox > federation foo. However I can confirm that a wave started on fedone and > containing only local fedone accounts works perfectly. > > I can also confirm that I get the same issue with two local and one > wavesandbox account. So it would appear that at some point, the sandbox > is returning a wrong hash count or the fedone mondgodb foo is storing > the wrong hashcount. > -- > James Purserhttp://wavingtheshiny.collaborynth.com.au > Wave Addresses: > [email protected] (wave.google.com) > [email protected] (wavesandbox.com) > [email protected] (collaborynth.com.au FedOne Server) > Skype: purserj1977 > GTalk: [email protected] -- 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.
