« Return to Thread: [RFC] Plugin specifc capabilities II
Re: [RFC] Plugin specifc capabilities II
by Graham Cobb-4
::
Rate this Message:
On Tue, March 31, 2009 12:22, Daniel Gollub wrote:
> as requested from me several times - i reviewed the entire Merger and
> Capabilities process.
>
> Please give me feedback on this! This is one of the last things i want to
> change for 0.39 - since this would require some tiny API changes. Once
> this is
> set i'm more then happy to tag and release 0.39.
>
> Since everyone wants really to see 0.40 - please make sure that we come
> very
> quickly on working solution for everyone ASAP.
Daniel,
I am away on holiday and will not have a chance to review this in any
detail until after Easter. I did glance at the Wiki pages and I am not
sure if this addresses the problems I found while trying to create the
capabilities for GPE: the merger process seems to need to be different for
data being sent to the device from OpenSYnc and data being received from
the device and sent to OpenSync. In particular, there is data which should
be included in the update sent to the device but which should not be
trusted when it is received from the device. This seems to mean that there
are three states neded for each attribute: supported, untrusted (specify
on send, ignore on receive), excluded (do not specify on send, ignore on
receive).
The second problem was granularity: how detailed the capabilities can be
(e.g. if the device can store a home and work address but not the various
different types of address which can be defined using the RFC). The only
short term API impact of this isue is that it shoud be possible to make
the capability definition files handle more granular capabilities in the
future without breaking the capabilities we define today. So, for example,
the format should allow us to define today that address is untrusted but
tomorrow we may extend the merger capabilities to specify that up to two
addresses are supported.
Sorry I am not in a position to review the proposals. Also, I do not know
when I will next have access to my mail while I am away, but I will leave
you to think about these!
Graham
------------------------------------------------------------------------------
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
> as requested from me several times - i reviewed the entire Merger and
> Capabilities process.
>
> Please give me feedback on this! This is one of the last things i want to
> change for 0.39 - since this would require some tiny API changes. Once
> this is
> set i'm more then happy to tag and release 0.39.
>
> Since everyone wants really to see 0.40 - please make sure that we come
> very
> quickly on working solution for everyone ASAP.
Daniel,
I am away on holiday and will not have a chance to review this in any
detail until after Easter. I did glance at the Wiki pages and I am not
sure if this addresses the problems I found while trying to create the
capabilities for GPE: the merger process seems to need to be different for
data being sent to the device from OpenSYnc and data being received from
the device and sent to OpenSync. In particular, there is data which should
be included in the update sent to the device but which should not be
trusted when it is received from the device. This seems to mean that there
are three states neded for each attribute: supported, untrusted (specify
on send, ignore on receive), excluded (do not specify on send, ignore on
receive).
The second problem was granularity: how detailed the capabilities can be
(e.g. if the device can store a home and work address but not the various
different types of address which can be defined using the RFC). The only
short term API impact of this isue is that it shoud be possible to make
the capability definition files handle more granular capabilities in the
future without breaking the capabilities we define today. So, for example,
the format should allow us to define today that address is untrusted but
tomorrow we may extend the merger capabilities to specify that up to two
addresses are supported.
Sorry I am not in a position to review the proposals. Also, I do not know
when I will next have access to my mail while I am away, but I will leave
you to think about these!
Graham
------------------------------------------------------------------------------
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
« Return to Thread: [RFC] Plugin specifc capabilities II
| Free embeddable forum powered by Nabble | Forum Help |
