7:38 p.m.
http://bugzilla.moblin.org/show_bug.cgi?id=7871
Summary: generate Server Alerted Notification (SAN) message +
peer configuration
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: ASSIGNED
Severity: normal
Priority: P1
Component: *Feature Request
AssignedTo: congwu.chen(a)intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
The message must contain:
- a server identifier and
- names for server-side data sources
which are recognized by the target device.
Typically phones are designed to work with a fixed PC-side software, often
Nokia's PC Suite. We have to emulate that behavior. It needs to be configurable
on a per-peer basis, because different peers might have different expectations.
The server identifier should be the local device ID, unless something else is
expected by the peer. We need a new configuration setting for this
("serverId"?), with "empty" meaning "use deviceId".
The data source names are a bit more tricky. We can't rename the
"addressbook",
"calendar", "todo", "memo" sources because the GUI and the
users expect them,
and because these names will be shared by different peers. We need per-peer
aliases.
I think this can be implemented like this:
- configure whether a peer configuration is for a client or server:
new configuration option "isClient" = false by default
- if true, the "uri" property is treated as a local alias for the
data source name
- these names are sent in the SAN
- the Synthesis engine XML configuration is created using the
aliases instead of the original name
- SyncContext::findSource() must get a parameter which tells it whether
it should use the aliases, false by default
- SyncEvolution_Module_CreateContext() and SyncEvolution_CreateContext()
must search based on the alias
--
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.
7:53 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |7873
--
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.
4:31 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #1 from Chen Congwu <congwu.chen(a)intel.com> 2009-11-17 21:31:31 PST
---
(In reply to comment #0)
The message must contain:
- names for server-side data sources
which are recognized by the target device.
Do you mean the "Server URI" field in SAN?
The server identifier should be the local device ID, unless something
else is
expected by the peer. We need a new configuration setting for this
("serverId"?), with "empty" meaning "use deviceId".
use "remoteIdentifier" for this purpose. If this is empty, fallback to
use
"deviceId".
The data source names are a bit more tricky. We can't rename the
"addressbook",
"calendar", "todo", "memo" sources because the GUI and the
users expect them,
and because these names will be shared by different peers. We need per-peer
aliases.
We don't rename them, just let "SourceConfig.uri" equals
each.
I think this can be implemented like this:
- configure whether a peer configuration is for a client or server:
new configuration option "isClient" = false by default
- if true, the "uri" property is treated as a local alias for the
data source name
- these names are sent in the SAN
The above has been done.
While I am not sure whether the following is necessary, could you explain? Take
addressbook as an example:
We have a local source (addressbook) at the server side(The folder
~/.config/syncevolution/$server/sources/addressbook) and tell the remote peer
contact us via the remote uri identified in
(~/.config/syncevolution/$server/sources/addressbook/config.ini:uri) which we
set it to "addressbook" intentionally.
This works for a simple Nokia phone sync.
- the Synthesis engine XML configuration is created using the
aliases instead of the original name
- SyncContext::findSource() must get a parameter which tells it whether
it should use the aliases, false by default
- SyncEvolution_Module_CreateContext() and SyncEvolution_CreateContext()
must search based on the alias
--
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.
7:14 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2009-11-18 00:14:46 PST ---
(In reply to comment #1)
(In reply to comment #0)
> The message must contain:
> - names for server-side data sources
> which are recognized by the target device.
Do you mean the "Server URI" field in SAN?
Yes.
> The server identifier should be the local device ID, unless
something else is
> expected by the peer. We need a new configuration setting for this
> ("serverId"?), with "empty" meaning "use deviceId".
use "remoteIdentifier" for this purpose. If this is empty, fallback to use
"deviceId".
I know we have remoteIdentifier. Is the fallback also in place? The comment for
the remoteIdentifier config property doesn't mention it, does it?
> I think this can be implemented like this:
> - configure whether a peer configuration is for a client or server:
> new configuration option "isClient" = false by default
> - if true, the "uri" property is treated as a local alias for the
> data source name
> - these names are sent in the SAN
The above has been done.
While I am not sure whether the following is necessary, could you explain? Take
addressbook as an example:
We have a local source (addressbook) at the server side(The folder
~/.config/syncevolution/$server/sources/addressbook) and tell the remote peer
contact us via the remote uri identified in
(~/.config/syncevolution/$server/sources/addressbook/config.ini:uri) which we
set it to "addressbook" intentionally.
This works for a simple Nokia phone sync.
For example, the Sony Ericsson K800i works with "remoteIdentifier" "Sony
Ericcs" and "Contacts" as URI for what we call "addressbook".
Source of this info:
http://opensync.org/wiki/peers/sonyEricsson/k800i
Perhaps we were lucky with the Nokia and it recognizes "addressbook".
--
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.
7:29 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #3 from Chen Congwu <congwu.chen(a)intel.com> 2009-11-18 00:28:59 PST
---
(In reply to comment #2)
I know we have remoteIdentifier. Is the fallback also in place? The
comment for
the remoteIdentifier config property doesn't mention it, does it?
Ah,
that's in my local branch.
> > I think this can be implemented like this:
> > - configure whether a peer configuration is for a client or server:
> > new configuration option "isClient" = false by default
> > - if true, the "uri" property is treated as a local alias for the
> > data source name
> > - these names are sent in the SAN
> The above has been done.
For example, the Sony Ericsson K800i works with
"remoteIdentifier" "Sony
Ericcs" and "Contacts" as URI for what we call "addressbook".
Source of this info:
http://opensync.org/wiki/peers/sonyEricsson/k800i
Perhaps we were lucky with the Nokia and it recognizes "addressbook".
The
example mentioned it workds with "Contacts" as URI, but did not mention id
didn't work with other URIs, have I missed something?
With Nokia, I just even tried with a source folder "adcde", it still works.
--
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.
8:43 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #4 from pohly <patrick.ohly(a)intel.com> 2009-11-18 01:43:34 PST ---
(In reply to comment #3)
> For example, the Sony Ericsson K800i works with
"remoteIdentifier" "Sony
> Ericcs" and "Contacts" as URI for what we call
"addressbook".
>
> Source of this info:
> http://opensync.org/wiki/peers/sonyEricsson/k800i
>
> Perhaps we were lucky with the Nokia and it recognizes "addressbook".
The example mentioned it workds with "Contacts" as URI, but did not mention id
didn't work with other URIs, have I missed something?
True. But to be on the safe side, we need a mechanism for phones where the URI
name matters.
With Nokia, I just even tried with a source folder "adcde",
it still works.
How does it know that "adcde" is meant to receive contact data and not memos or
events? My only explanation is that it matches unrecognized strings to
contacts.
Can you get this Nokia phone to synchronize also the other data categories?
--
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.
8:46 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #5 from Chen Congwu <congwu.chen(a)intel.com> 2009-11-18 01:46:41 PST
---
(In reply to comment #4)
> With Nokia, I just even tried with a source folder "adcde", it still
works.
How does it know that "adcde" is meant to receive contact data and not memos
or
events? My only explanation is that it matches unrecognized strings to
contacts.
That's because the MIMEType in the SAN.
Can you get this Nokia phone to synchronize also the other data
categories?
Yes, basically contacts, calendar, todo, memo all works.
--
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.
9:04 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2009-11-18 02:04:29 PST ---
(In reply to comment #5)
(In reply to comment #4)
>
> > With Nokia, I just even tried with a source folder "adcde", it still
works.
>
> How does it know that "adcde" is meant to receive contact data and not
memos or
> events? My only explanation is that it matches unrecognized strings to
> contacts.
That's because the MIMEType in the SAN.
Interesting. That's a usage of the MIME type that I didn't dare hope for. From
what I heard before, it seemed that the URI would be used.
--
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.
9:18 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #7 from pohly <patrick.ohly(a)intel.com> 2009-11-18 02:18:48 PST ---
(In reply to comment #5)
(In reply to comment #4)
>
> > With Nokia, I just even tried with a source folder "adcde", it still
works.
>
> How does it know that "adcde" is meant to receive contact data and not
memos or
> events? My only explanation is that it matches unrecognized strings to
> contacts.
That's because the MIMEType in the SAN.
> Can you get this Nokia phone to synchronize also the other data categories?
Yes, basically contacts, calendar, todo, memo all works.
Wait, there's one snag: how does the phone decide whether "text/x-calendar"
is
for VEVENTs (our calendar datasource) or VTODOs (our todo)?
Does it perhaps send both for the same source? Then we need the joined
datasource configuration (#4611). However, in this case I would expect the
phone to reject a SAN where two different sources have the same
"text/x-calendar" type.
--
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.
12:22 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #8 from Chen Congwu <congwu.chen(a)intel.com> 2009-11-19 17:22:10 PST
---
(In reply to comment #7)
Wait, there's one snag: how does the phone decide whether
"text/x-calendar" is
for VEVENTs (our calendar datasource) or VTODOs (our todo)?
Does it perhaps send both for the same source? Then we need the joined
datasource configuration (#4611).
That's exactly the problem.
However, in this case I would expect the
phone to reject a SAN where two different sources have the same
"text/x-calendar" type.
I think a Nokia phone stores todo and calendar
together so they will not think
them as two different sources.
--
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.
10:33 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #9 from pohly <patrick.ohly(a)intel.com> 2009-12-11 03:33:41 PST ---
(In reply to comment #0)
I think this can be implemented like this:
- configure whether a peer configuration is for a client or server:
new configuration option "isClient" = false by default
- if true, the "uri" property is treated as a local alias for the
data source name
Just noticed that this is trivial to implement: there's an <alias> tag for
<datastore> in the Synthesis XML config.
--
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.
7:07 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
--- Comment #10 from Chen Congwu <congwu.chen(a)intel.com> 2009-12-29 00:07:04 PST
---
(In reply to comment #9)
Implemented in commit
7b034a5cf5eca97579ac82b8d9d4e7ef15072504
(In reply to comment #0)
> I think this can be implemented like this:
> - configure whether a peer configuration is for a client or server:
> new configuration option "isClient" = false by default
> - if true, the "uri" property is treated as a local alias for the
> data source name
Just noticed that this is trivial to implement: there's an <alias> tag for
<datastore> in the Synthesis XML config.
--
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.
6:16 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
Chen Congwu <congwu.chen(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #11 from Chen Congwu <congwu.chen(a)intel.com> 2010-01-05 23:16:04 PST
---
Considering this been fixed.
--
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.
8:12 p.m.
New subject: [Bug 7871] generate Server Alerted Notification (SAN) message + peer configuration
http://bugzilla.moblin.org/show_bug.cgi?id=7871
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #12 from pohly <patrick.ohly(a)intel.com> 2010-02-04 01:12:42 PST ---
Let's test this as part of normal functional testing.
--
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.
4609
days inactive
4696
days old
syncevolution-issues@syncevolution.org
13 comments
1 participants
participants (1)
-
bugzilla＠moblin.org