On Tuesday 05 February 2013 07:44:00 Patrick Ohly wrote: > On Mon, 2013-02-04 at 22:49 +0000, Graham Cobb wrote: > > Or, do I make it much more simple: if the string matches a CollectionId > > use that, else if the string matches a folder path name use that, else > > return an error (actually, I would probably force a FolderSync and try > > again before returning an error). And if you give your folders names > > which are the same as CollectionIds of other folders, more fool you (you > > can always use the CollectionId). > > That's the way how the other backends work. This has not caused problems > in the past, so perhaps its good enough. It would also be consistent > across backends.
Thanks for the advice. That is what I will do, with one very small twist: it will be possible to specify a folder path with a leading /, which will be ignored (except to indicate this is a path, not a collection Id). This means that if you have created folders 1, 2 and 3 you can specify them by folder name if you want (/1, /2, /3). getDatabases will continue to display the names without a leading / and most people only use top level folders and will never use a / but it is there if someone wants to use it. Graham _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
