El 23/06/11 23:55, Soren Lassen escribió:
> Yes, most of the documentation is still at waveprotocol.org but will
> eventually be migrated to the Apache Wave website
> http://incubator.apache.org/wave/ and wiki.
> 
> Persistence is described here:
> http://www.waveprotocol.org/protocol/design-proposals/wave-store-design-for-wave-in-a-box
> It says "this file system based design is less scalable than a
> database system like MongoDB and therefore we expect to revisit the
> design later to scale it better", but I don't think anyone is working
> on it.
> 
> At the time we implemented the file based persistence, mongodb lacked
> the necessary facilities to acknowledge when data reached durable
> storage. That has been added now and there should be no technical
> roadblocks to implement the storage interfaces with mongodb. The code
> is structured in a way that should make that straightforward if anyone
> is interested in doing it.
> 
> Soren

Thanks Soren for the summary.

What about to make a specific and temporary working group with people
interested in this issue?

What about a specific wiki page (or even a wave) to work on it? There
people that knows better the "state of art" of this issue can describe
it, and people that want to contribute (like me), can try to.

Can Datanucleus be an option? (thinking about GAE)
http://www.datanucleus.org/products/accessplatform_3_0/mongodb/support.html

If anybody decide to create a wave about that, feel free to add me:
[email protected]
[email protected]

Bests,
-- 
Vicente J. Ruiz Jurado

http://comunes.org
http://ourproject.org
http://homes.ourproject.org/~vjrj/blog

 "Our hope is that this project will inspire similar efforts at other
 institutions and will reinforce the concept that ideas are best viewed
 as the common property of all of us, not as proprietary products
 intended to generate profits." [William and Flora Hewlett Foundation
 president Paul Brest, commenting on the foundation's support for the
 Massachusetts Institute of Technology's OpenCourseWare initiative]


Reply via email to