triAGENS/ArangoDB — pull request #216 by jsteemann (2012-10-04 13:12:11+00:00)
Title: possible implementation for issue #213

the attached commit presents a possible solution for this:
when using the HTTP POST/PUT/DELETE methods, the waitForSync URL parameter can be used to force synchronisation. If it is ommitted or set to false, everything will work as before: there will be synchronisation if the flag was set for the collection that is modified during the operation.
If the waitForSync URL parameter is set to true, then synchronisation is forced after the operation, even if the collection-level flag is set to false.

That means one can use the flag to force synchronisation of individual operations in case that waitForSync is set to false on collection level. It cannot be used to turn off synchronisation for certain operations when waitForSync is set to true on collection level.

If we want to go ahead with this implementation, please pull this into devel.

Documentation for the changes is still missing as I wanted to avoid unnecessary work in case we discard the pull request.