← Back to team overview

tomdroid-dev team mailing list archive

Re: a note's last-change-date


On Sat, Jan 23, 2010 at 1:22 AM, Sandy Armstrong <sanfordarmstrong@xxxxxxxxx
> wrote:

> If there is a better "universal" datetime format (for example, just
> using Zulu), then let's figure that out and we can update the REST API
> spec to be a little more specific about what datetime formats it
> accepts and what format it returns.  Fixing Snowy would be easy here;
> I can't speak for the U1 guys, I guess it depends on how they store
> the dates.

After some more research I found out that tomboy's time format is not your
usual ISO 8601 and that saying RFC 3339 is more specific.

Anyway, I've found a fast android sdk class that parses rfc3339 so I can
drop the big and expensive jodatime library (a 200k jar).

There is one remaining problem is with millisecond precision. Usual rfc3339
datetime is:


And tomboy has more than millisecond precision:


So I'm getting a parse error where the +/- character should be.

Short term, I'll regexp out the additional precision and store in the
database using UTC (to avoid sqlite's own problems). Foreseeable problems
doing that?

Long term, we could try to agree on a dateformat that is accessible from
standard libs in Java, C#, Python, C/C++ with minimal fuss. I'm interested
in changing the note spec not only the REST API because I feel that a
portion of users want the note files to be portable and would not
necessarily want to trust a cloud service.

Thanks for the help! It's very nice to port an application when the dialogue
is good with the current maintainer. Cheers to Sandy!
Olivier Bilodeau <olivier@xxxxxxxxxxxxxxxxx>