Hi! So, there is no planning for future MongoDB support? As i see for now - there is no activity on SQL persistence topic also
As i think - for stable future of WIAB - there should be support for mature - yet easy to config - SQL DB(i suggest PostgreSQL for start) with really stable search platform (i think - Apache Solr) working in most cases, and I cant see - why to build-invent own-verycustom WIAB search-DB solution, with bugs, not working with most easy to start-on hosting companyes.. if there are many 'standart' solutions for projects with such scale? Building with SQL+popular search platform - WIAB could achieve reputation of nice - easy scallable opensource product, that one could build in almost every existing server-structure without reconfiguring whole site-system rather than becoming - small pro-community driven - read tons of tutorials - rewrite by yourself - ask in group - structure.. If there at last - a chance to fully bring WIAB to masses in many countries and so, why to nigilate it with so many hard to implement-here solutions? I'm sorry for such emotional post, but i know for sure - MANY people all over the world - love the Wave idea, waited for stable federation release to start building cool - trans-community social networks, when you personally can - change - reconfig -restyle what you want for your site-forum community, and still - have a chance to easy invite other site's community to yours without openid's fb's or other - not so cool options, wave federation - seemed like beautiful semantic web platform for such a small revolution , you know. And with approach like i see - now - if there will be package-suitable option for simple installation - integration into existing site platforms - for not so tech savvy people, it will be in best case - in half a year or so - simply - by negotiating relatively simple opensource java(i still think Python is better for fast groving - many commiters comunity) approach by hard to deal with Search-DB solutions Am i wrong? On Dec 22, 12:42 am, Alex North <[email protected]> wrote: > Inspired by community enthusiasm we initially attempted a MongoDB > implementation. Further investigation showed that Mongo was not suitable for > a single-server installation, the basic case for Wave in a Box. Mongo > doesn't offer suitable durability guarantees. > > We decided to make a pure filesystem implementation because it's > conceptually very simple (append-only) and demonstrates exactly what is > required from a wave store. There's few abstraction layers to get in the > way. Note that this is only for the simple wave/account/certificate stores; > more complex structures like the upcoming index make less sense to implement > directly on disk. > > On 21 December 2010 23:04, Yuri Z. (a.k.a Vega) <[email protected]> wrote: > > > > > > > > > By the way, why the current persistence approach is File system based > > and not say DB based? Is it easier? I am just curious. > > > On Dec 21, 5:00 am, Alex North <[email protected]> wrote: > > > Well, we've been saying "any day now" for many weeks, so I can't honestly > > > predict it. > > > > Also, even when persistence is implemented, it will probably come with a > > big > > > red warning sticker that the on-disk representation is not stable and > > will > > > probably change a couple of times until we're confident it's something we > > > can retain backwards compatibility with. > > > > Alex > > > > On 21 December 2010 12:34, bluecobalt <[email protected]> wrote: > > > > > How soon is "soon"? Wave is unusable for us until we can safely store > > > > waves. > > > > > On Dec 20, 4:45 pm, Alex North <[email protected]> wrote: > > > > > Not yet, but soon! > > > > > > On 21 December 2010 03:32, BuggyB <[email protected]> wrote: > > > > > > > Hi... > > > > > > Is it possible by this time to store/save the waves in a database > > > > > > system or anywhere? > > > > > > > When I restart my server, the waves will go away ... > > > > > > > -- > > > > > > 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%2bunsubscr...@goog > > > > > > legroups.com> > > <wave-protocol%2bunsubscr...@goog legroups.com> > > > > <wave-protocol%[email protected]<wave-protocol%252Bunsubscribe > > > > @googlegroups.com><wave-protocol%252Bunsubscribe > > @googlegroups.com> > > > > > > > . > > > > > > 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]<wave-protocol%2bunsubscr...@goog > > legroups.com> > > . > > 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.
