>> 1. what is the status of the mongodb provider? is someone using it already >in production? looking at the code it seems to be not threadsafe concerning >the CRUD handling with non-synchronized hash maps. > >Afaik, there are people using that code slightly modified (not sure what >the changes are) in production. I think the impl is thread safe as a >resource provider by itself must not be thread safe. But if it's not, we >should fix it.
ah, i see. each resource resolver gets its own instance of resource providers, so the resource provider itself does not have to care about concurrency because resource resolver is not thread-safe either. this makes the implementation simpler. >In general it would be cool to have some more/better NoSQL support in >Sling to attract devs using these storages. ok - my next plan is to create a branch for a proof of concept couchbase resource adapter including a proposal for a shared part of nosql providers (and create a ticket for further discussion). stefan
