[Shr-Devel] New features in opimd queries
Sander van Grieken
sander at 3v8.net
Mon Aug 31 11:01:14 CEST 2009
On Thursday 27 August 2009 12:14:29 Michael 'Mickey' Lauer wrote:
> On Thursday 27 August 2009 12:07:09 Sebastian Krzyszkowiak wrote:
> > And:
> > > The Problem with a timestamp string is: what format does it have? In
> > > this case we have to include the format defenition into the API. Then
> > > it's a lot easier to use unix-timestamps they are easy to parse and
> > > compare...
> > In my opinion we should use unix timestamps and that's what i'm
> > implementing in my test apps.
> Correct. Epoch(UTC) should be the native format on dbus API level, but
> remember to include a flag that indicates whether timestamps are always
> following local time or stick to the timezone they have been entered (which
> could be handy at times). UI can convert this to fancy things.
IMHO all PIM related timestamps should almost always stick to the timezone. Isn't it
better to allow any representation on the API level and do conversion inside opimd? That
way the conversion logic doesn't need to be duplicated in every UI.
More information about the smartphones-standards