--- Comment #35 from yongsheng zhu <yongsheng.zhu(a)intel.com> 2010-02-28 18:18:02
(In reply to comment #34)
(In reply to comment #31)
> >+ /** the 'syncURL' used by synchronization */
> >+ string m_url;
> >Wouldn't it be easier to use the vector<string> returned by
> >you don't have to do your own parsing. Or is this not a copy of the
> >"syncURL" property, as the comment implies?
> we have to parse, because we want to know whether a syncURL is enabled to auto
> sync according to 'autoSync' property.
Yes, but where is the parsing done? Is this m_url still the comma-separated
value from "syncURL" or is it already a single URL after parsing?
syncURLs are parsed when initialization or updated. a single URL for one task.
once an interval has passed, if transport for the URL is present, put it in the
working queue. Else, not.
When doing running, SyncContext only picks the first URL as the used URL, so if
combining them, we also have to iterate parsed syncURLs again and set sync used
URL temporarily one by one.
(In reply to comment #33)
> > > I'm not sure whether we need this level of detail. It makes
> > > notification harder in the backends. What would the "bool raw"
> > > anyway?
> The same as the 'raw' parameter in insertItem, readItem,meaning item in
> internal format instead of engine format.
But what does that mean in the context of change notification? When is the
parameter supposed to be true, when false?
true - internal format
false - engine format
maybe it's my misunderstanding.
(In reply to comment #30)
> > I'm not sure whether we need this level of detail. It makes implementing
> > notification harder in the backends. What would the "bool raw"
> > anyway?
> currently we don't need this kind of detail(only know it does change). but I
> don't know whether there are other requirements for this.
An API can be both too limited and too complex. When it is too complex,
implementing it is unnecessarily hard. In this case I think the API is too
complex. My philosophy is that we shouldn't try to solve problems that don't
ok, so 'void itemChanged()' is enough for we even needn't
know which item is
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.