On Wed Nov 25 14:52:38 2009, Robin Collier wrote:
If the item is timestamped, it determines order so no round trip to
the server
is necessary. Of course a version attribute with a natural order
on the item
would do this as well. How does this not solve this problem? This
of course
assumes that the timestamp is not the same for two different
versions of the
same item (as I have said would be required before).
The only possible reason to want a timestamp is if you want to
synchronize ordering between two independent sources, and don't mind
the risks that entails.
Otherwise, there's nothing gained by a timestamp - including an
ACAP-style modtime - that isn't gained by either a strictly
increasing integer, or an opaque string which the server can do
something useful with.
This is not to say that timestamps have no place in PubSub, but
whether or not they're the right solution depends entirely on your
goals.
I'm not clear on what anyone's goals are, currently, but I would note
that if you want to - for example - try to avoid PEP events that
you've probably received already, then a timestamp in the presence
would seem like a sensible option. Whereas if you want atomicity in a
pubsub event stream, such that events are delivered once and once
only over an unreliable network, then it's probably not the tool
you're looking for. (Or it might be, but only if the timestamps are
ACAP-style modtimes, which are designed to satisfy both - with some
risk involved as usual).
On a different note, your mail tool seems to make it difficult to
do replies that
actually mark the existing text. I have to manually indent for the
replies, which
I haven't had an issue with on any elses messages. What tool are
you using?
He's using Apple Mail 2. Sadly not doing format=flowed, butthe
text/plain part is reasonable. But yes, you're highlighting the
reason why people suggest avoiding HTML messages on mailing lists.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
