[JDEV] Message timestamps

[Scott Robinson]

I receive the argument of ISO 8601 in that:

a) it's a good mix between readability and code-level
b) it forces Jabber clients to not breakdown in syntax as many mail clients
do.

RFC-822 _IS_ Y10K compliant with a _very_ simple (non-standard breaking)
change. =p

Scott.

* Benjamin Holzman translated into ASCII [Mon, Oct 04, 1999 at 06:50:34PM -0400][<37F92F3A.51B3D13E at orientation.com>]
> Vivre Draco wrote:
> > 
> > On 4 Oct 99,, Benjamin Kahn sounded off on Re: [JDEV] Message timestamps:
> > 
> > >       Or, how about the number of seconds since 1970?  If we are
> > > worried about year 2038 issues, we can use a 64-bit number.  ;^)
> > 
> >    IMHO, a human-readable format is highly preferable -- it minimizes
> > the client requirements, which seems to be one of Jabber's
> > philosophies. The ISO 8601 or SMTP standards look like the best
> > options so far.
> > 
> 
>                ISO 8601                 RFC 822
> Advantages:    Concise                  Somewhat Concise
>                Always GMT               Human-readable
>                Sorts lexicographically
> Disadvantages: A tad cryptic            Not always GMT; can be confusing
> to clients
>                Not Y10K compliant       Not Y10K compliant
> 
> -- 
> |        Ben Holzman                       bah at orientation.com       |
> |      orientation.com                     Tel: +1 212 966 5553 x219 |
> |  Senior Software Engineer                Fax: +1 212 966 5554      | 
> $ perl -l040e 'print ucfirst for reverse qw/hacker perl another just/'
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>