[SyncEvolution] phone branch merging
by Patrick Ohly
Hello Congwu!
Is the "phone" branch ready for merging? It seems that at least the
"initiate slow sync" part still needs some work or cleaning up.
I'd can merge this after fixing the compiler warnings on the current
master later today, if you want.
I've looked at the code. Some comments:
Server Alerted Sync: SAN generation
ContentType in the 'Get' command during the SAN should be XML or WBXML instead
of SAN Notification.
Why that? Perhaps I misunderstand the code, but doesn't it ensure that
the content type for the SAN message is
TransportAgent::m_contentTypeServerAlertedNotificationDS and *not* XML
or WBXML?
FileSyncSource: use x-vcalendar instead of x-calendar
This changes user-visible behavior, and not just in the FileSyncSource,
doesn't it? I agree that x-vcalendar is the better choice, but
x-calendar should still be accepted for users who have it in their
configs.
Join/dejoin Mutiple SyncSources, MB#4611
Can you move the escape code for the new virtual backend's
evolutionsource property into util.cpp? It's likely that we'll also need
it for multiple syncURLs.
+ "If the backend is a virtual data source, \n"
+ "this field points a comma seperated list of \n"
+ "sub datasources actually used for syncing.\n"
+ "If your sub datastore has comma in name, you\n"
+ "can separated by preceding it with '\\' \n"
Extra white space - evil! ;-) Spelling improvement:
"If the backend is a virtual data source,\n"
"this field must contain a comma separated list of\n"
"sub datasources actually used to store data.\n"
"If your sub datasource has a comma in its name, you\n"
"must prevent that comma from being mistaken as the\n"
"separator by preceding it with a backslash, like this:\n"
" evolutionsource = Source1PartA\,PartB, Source2\\Backslash\n"
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
12 years, 5 months
[SyncEvolution] questions about sync reports
by Jussi Kukkonen
Hi,
I was working on improving the error reporting in the UI, and got some
questions:
It seems that at least some failing syncs do not generate a report: I
tried setting a wrong password and syncing. When I asked for a report
afterwards, I got the one for the last successful sync. Is this what I
should expect?
The GetReports BNF documentation was very good for writing the parser,
but I'm still a bit confused about some of the fields:
* status
Only value I've seen is 200, and git log tells me this is a successful
sync. Does this otherwise correspond to error in StatusChanged?
* source-X-status
This seems to be '0' all the time. I assume this correponds to error
values in sources hash in StatusChanged signal?
* source-X-mode
This was "two-way" even when I set "none" for this source.
* source-X-resume
?
12 years, 5 months
[SyncEvolution] Using backends not in /usr/lib/syncevolution?
by John Dykstra
Is there any way to tell syncevolution to look somewhere else
than /usr/lib/syncevolution/backends for its backends? (I don't have
write access to /usr on my work machine.)
If this currently isn't implemented, leveraging LD_LIBRARY_PATH might be
a good way to do it.
-- John
12 years, 5 months
Re: [SyncEvolution] Test cases design for DBus server: Status and Progress
by Patrick Ohly
On Fri, 2009-11-27 at 06:17 +0000, Zhu, Yongsheng wrote:
> I write some test cases design for GetStatus/StatusChanged signals and
> GetProgress/ProgressChanged signals.
> Please see the attachment.
Looks reasonable. I was wondering whether those tests which run a full
sync should be combined. Advantage: shorter overall runtime.
Disadvantage: the different aspects cannot be tested independently. Your
choice (that way I don't have to decide ;-)
> But it seems that it is hard to do checkings for
> GetProgress/ProgressChanged accurately.
That's true. Basic sanity checking as you suggested (increasing
progress, etc.) looks reasonable.
Regarding test-dbus.py in general: some method of controlling the
currently hard-coded global settings would be useful, together with
documenting them.
I didn't do that initially because it wasn't sure how useful the script
and individual options are, but it seems to be useful, so let's make it
not just useful, but also nice.
One option that I keep changing in the source often is
debugger = "gdb"
to enable an interactive debug session of the syncevo-dbus-server during
a test.
The other option that at least needs to mentioned is the dependency on a
valid HTTP server configuration, currently hard-coded at
"scheduleworld_1".
--
Best Regards
Patrick Ohly
Senior Software Engineer
Intel GmbH
Open Source Technology Center
Hermuelheimer Strasse 8a Phone: +49-2232-2090-30
50321 Bruehl Fax: +49-2232-2090-29
Germany
12 years, 5 months
[SyncEvolution] confused about defaultPeer
by Jussi Kukkonen
Hi,
This was something I've been meaning to ask, but keep forgetting: How am
I supposed to use defaultPeer configuration item?
This is what I'm trying (no non-default contexts or anything):
1. On UI startup: Call Server.GetConfig() onto get config value
{"","defaultPeer"}. I assume using "default" as configuration/template
name would work.
2. When saving a configuration and setting it as default: Call
Session.SetConfig() for configuration <name> with {"", "defaultPeer",
"<name>"} in it.
The problem is that defaultPeer seems to get saved in <name>/config.ini
instead of global config.ini. What am I doing wrong?
- Jussi
12 years, 5 months
