[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-format
Subject:    Re: libkolabxml: When setting a start/end/etc. ...
From:       "Georg C. F. Greve" <greve () kolabsys ! com>
Date:       2012-07-16 11:12:29
Message-ID: 19744185.v4SeICAvR7 () katana ! lair
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 16 July 2012 11.49:44 Jeroen van Meeuwen wrote:
> Right - how does one treat a floating-time in scheduling (the Python 
> equivalent is a naive datetime) - create a 48 hour margin of error?

Well, the value makes more sense for users, as their client will then always 
display it at the local time set by the user.

I guess the interpretation of such a value for resources would be the time 
zone of the resource, which for some resources (corporate jets) could be 
changing, and otherwise would probably be the same as the office.

As for "office time" I guess server time might serve as the ultimate fallback, 
but this is perhaps something we want to allow to configure per server and 
perhaps also per resource.

Best regards,
Georg


-- 
Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Zürich, Switzerland

e: greve@kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
["signature.asc" (application/pgp-signature)]

_______________________________________________
Kolab-format mailing list
Kolab-format@kolab.org
https://www.intevation.de/mailman/listinfo/kolab-format

[prev in list] [next in list] [prev in thread] [next in thread]