Actually, Tad Glines and I were thinking about collaborating on a SQL Persistence module either through JPA or Apache JDO. I suspect we will get going on this some time soon after we migrate over to Apache. It will be a rather large chunk of coding and I am pretty sure we would wind up moving repo's during the middle if we started now.
That said any help would be more than welcome. ~Michael On Dec 21, 2010, at 4:35 PM, James Purser wrote: > (Bringing this over to the wave-dev list on apache) > > Hi Kyngar, > > Actually what is missing for MongoDB or SQL perisistance is someone to pick > them up and run with them. While the file based persistance is probably the > lowest hanging fruit delta persistance wise, there is nothing stopping > anyone from contributing code which allows people to use MongoDB or any > other data storage method. > > If you want to pick it up, then I would love to see it, and I think if you > can show a good design or code chunk then I think you'll find people are > perfectly willing to help out. > > James > > On Wed, Dec 22, 2010 at 11:07 AM, Ya Knygar <[email protected]> wrote: > >> 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? >> >> -- >> 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.
