[JDEV] Message timestamps

[Daniel Arbuckle]

The ISO standard seems to be harder to screw up on. That's a major plus in
my opinion. If the client can't parse the information reliably, it's
useless.

Regarding the location where timestamping is performed:
Obviously the timestamp should be inserted by the server; otherwise evil
clients could spoof the information. But it's not enough to say "the
server" should do it, because there are probably more than one server. If
the timestamp represents the time the message is sent, then the sender's
home server should apply the timestamp -- unfortunately, this also leaves
open the possibility of spoofing. If the timestamp represents the time
when the message arrived in your mailbox, then your own home server should
apply it to the message.

The question is: "what does the timestamp represent?"

Daniel

On Mon, 4 Oct 1999, Steven Wagner wrote:
> Good point Scott.  Maybe we should consider which standard a programmer would be less likely to confuse or
> misinterpret.  There are obviously going to be many 3rd party clients in the future, probably some sloppy ones
> also if Corel is planning on making one, and we don't want the date getting messed up.
> Is the time date stamping going to be done on the server-side?  I hope so.  If it is, maybe my above point isn't
> as important.  :)
> 
> Steven
> 
> Scott Robinson wrote:
> 
> > I would like to touch on processing time. It was mentioned in a previous
> > post that the ISO standard would be easier for a program to decode than the
> > RFC. I would note that once the C/C++ is written, the encode/decode times
> > are minimal if not non-existant.
> >
> > Scott.
> >
> > * Steven Wagner translated into ASCII [Mon, Oct 04, 1999 at 04:37:28PM -0700][<37F93A38.3E2DA99A at impulse.net>]
> > > As long as we avoid the problem that email has of email clients all having many
> > > different date formats.  Which one is it that does that?  Im confused.
> > >
> > > I think we should go with the date that is the most effecient for compatibility
> > > and readability by the code.  I don't think we should go with straight binary,
> > > but something that is more code effecient should be better then something that
> > > is more human readable.  The client is going to have to parse the date apart
> > > anyways so that it can display it in whichever way the user chooses (or are we
> > > not going to give them a choice?)
> > >
> > > I hope my input is valid.
> > >
> > > Steven
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > jdev mailing list
> > > jdev at jabber.org
> > > http://mailman.jabber.org/listinfo/jdev
> > >
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>