Marcus, its due to CS API convention - all apis added after 2.x version of CS, should be async (except for list* commands). It was designed this way after hitting the problem when initially some commands were sync (as only db updates were done as a part of it), then some backend calls were added to them which require them to become async. And it used to break API backwards compatibility.
To avoid situation I¹ve described above, we¹ve decided that all new commands should be async no matter if they contain backend operations, or not. -Alena. On 4/22/14, 10:03 AM, "Marcus" <shadow...@gmail.com> wrote: >Can anyone tell me off the top of their head why the createTags call is >async? Is it doing something other than inserting a db entry? Or perhaps a >better question is where the threshold is for sync vs async, for example, >createNetwork is sync, but is rather blocky.
