Re: [SyncEvolution] status (error) value constraints
Ohly, Patrick wrote:
On Tue, 2009-12-15 at 10:54 +0000, Jussi Kukkonen wrote:
> I've phrased these as questions so no-one takes these as explanations of
> status quo: I really couldn't tell what to expect.
>
> * if there is a non-zero source status, will sync status be non-zero?
Yes.
> * Can there be different sources with different non-zero source status
> codes in a single sync?
Yes. To give one example, the uri in addressbook might be wrong (=> 404,
or something like it) and the server might fail to process and item sent
for calendar (=> 500, depending on server).
Ok. Is it then enough to handle just the source statuses, or is there
some information in the generic sync status that I need to look at in
addition?
Context: I'm trying to decide where to show errors. It looks like I'll
do one or both of two things depending on the situation:
1. infobox right under the service name. Example:
ServiceName
Failed to login. Could there be a [ Edit settings ]
problem with your settings?
2. Infobox right below the source name:
ServiceName
SourceName
There's a problem and a normal sync [ Fix it ]
is not possible.
> * StatusChanged signal can obviously include zero status and
later
> non-zero status. Can one source have several non-zero statuses (as in
> 0 -> LOCERR_USERSUSPEND -> LOCERR_TIMEOUT)?
Not with the current implementation. But I would prefer to not make that
part of the API description. Is that a problem the the UI?
No. I plan to stop handling the status codes in StatusChanged
altogether: the information is not really that useful during sync, and
afterwards I'll do GetReports() anyway. I was trying to find out if I'll
lose important info if I do that -- it seems not at the moment at least.
- Jussi
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.