http://bugzilla.moblin.org/show_bug.cgi?id=9347
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|Undecided |P2
Status|Waiting for upstream |ASSIGNED
Target Milestone|--- |1.0
Severity|normal |major
--- Comment #7 from pohly <patrick.ohly(a)intel.com> 2010-02-04 05:21:23 PST ---
(In reply to comment #6)
>SyncEvolution uses a device id (i.e. source URI) with a format
that is already
>being used by Funambol clients: sc-pim-1b6ce05d-a34e-4157-aa77-4a19896b5126.
>We use the source URIs to determine devices and enable workarounds for all kind
>of problems with certain clients.
The source URI is an opaque string. There are other, standardized methods to
detect clients, like the DevInf, which is properly filled in by
SyncEvolution/Synthesis.
Very old Funambol clients didn't send proper
>DevInf data, so we always use Funambol's SIF format if we see a device that we
>consider a Funambol client.
Then Horde should use the source URI fallback only when the DevInf is
incomplete.
Shall I attach my configuration, so we can create a new template for
horde
groupware servers?
Yes, please. However, the identifier is not part of the template, it is
hard-coded in source code.
We cannot change it there, because the Funambol server itself requires us to
provide the sc-pim- prefix. Otherwise it won't allow multiple SyncEvolution
instances to talk to the same user account.
Both Funambol and Horde should be fixed to not depend on what we send in that
field.
The only client-side solution that I see is to make the prefix configurable as
part of the server template.
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.