I am working on adding --print-databases support in the activesync backend.  
In fact I have it working but it has raised a few questions:

1) Activesync needs an account before it can connect to a server and get the 
folder list.  I think that WebDav has the same issue.  And, in fact, I stole 
the solution from the WebDav code: insist that the source has a username 
configured.

The effect of this is that using just "syncevolution --print-databases" 
doesn't show anything, even if you do have an account configured.  In fact, 
you have to name a "target-config" configuration, and exactly one source, to 
get the listing.  You can't even set up any configuration of the default 
context which will allow "syncevolution --print-databases" to work.

Is this expected and desired behaviour?

2) This leads to another question.  Other getDatabases implementations only 
list databases of the same type as the particular source.  However, 
particularly as you can't specify several sources at the same time in the 
--print-databases command, I am inclined to list all the folders (of all 
types) whatever source is specified.

Would that be regarded as a problem (it also makes the code easier :-))?

3) libeasclient exposes an API to list the databases.  Unfortunately it is 
exposed by the libeasmail code (eas_mail_handler_get_folder_list).  libeasmail 
is not used anywhere else in the activesync backend and, in fact, doesn't even 
seem to be usable (the libeasmail.h header file depends on several internal 
header files which are not installed)! Is any application actually using 
libeasmail?

eas_mail_handler_get_folder_list works (if I manually copy the parts of the 
header file that are needed).  But I would prefer to use an API exported by 
libeassync as I don't see listing folders as mail-specific.  That would mean 
adding a new function exported by libeassync and bumping the soname.  
Actually, I don't see that the library currently uses sonames -- is that 
right?  It would mean, in any case, that the new syncevolution backend would 
require the new version of the libeasclient library to build.  Any problem 
with that?

Graham
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to