beagle r3446 - in branches/beagle-0.2.16: BeagleClient Util libbeagle/beagle search/Tiles

[joeshaw svn gnome org]

Author: joeshaw
Date: 2007-02-13 19:27:51 +0000 (Tue, 13 Feb 2007)
New Revision: 3446
ViewCVS link: http://svn.gnome.org/viewcvs/beagle?rev=3446&view=rev

Modified:
   branches/beagle-0.2.16/BeagleClient/QueryPart.cs
   branches/beagle-0.2.16/BeagleClient/Versioned.cs
   branches/beagle-0.2.16/Util/DateTimeUtil.cs
   branches/beagle-0.2.16/Util/StringFu.cs
   branches/beagle-0.2.16/libbeagle/beagle/beagle-timestamp.c
   branches/beagle-0.2.16/search/Tiles/IMLog.cs
   branches/beagle-0.2.16/search/Tiles/MailMessage.cs
   branches/beagle-0.2.16/search/Tiles/Utils.cs
Log:
Merge r3417, r3418, r3424 and r3429 onto the branch.

r3417:
Directly parse BeagleTimeStamp instead of calling DateTime.ParseExact.
Remove some duplicate code from beagle-search.

r3418:
FAQ 1. My application uses datetimes from different sources. I also have
to store it on disk.
*      Always convert any datetime to UTC and use it in that form for
*      internal usage. UTC is a good general framework.
FAQ 2. My application is a client server app that needs to send and
receive datetimes.
*      XmlSerializer assumes localtime by default when deserialing.
*      Hence, either change time to localtime before serializing or send
*      a string representation of the UTC time and re-construct the
*      correct time at the other end. The timezone part of the
*      serialized timestamp does not mean anything useful and should be
*      ignored completely.

Beagle does 1. Beagle should have done 2 but everytime the datetime
serialization problems were avoided using other fixes. This patch sends
the datetime in its string representation. Also instead of printing the
timezone in the output of beagle-query, print the datetime kind. As I
said, the timezone does not say anything useful.

r3424:
Remove a debugging line I accidentally committed.

r3429:
Fixing a buildbreaker