[JDEV] Message timestamps.
tcharron at ductape.net
Sat Oct 9 12:13:57 CDT 1999
Quoting Scott Robinson <quad at jabber.org>:
> * Thomas Charron translated into ASCII [Fri, Oct 08, 1999 at 06:14:32PM
> 00][<199910082314.SAA18561 at ductape.net>]
> > Quoting Daniel Arbuckle <djarb at wvc-omak.ctc.edu>:
> > Yes, but in order to properly implement this, we're now going to force
> > to start parsing XML out of the messages, which it should NOT be doing.
See Below.. ;-P I think you got what I meant later..
> > see, to the TRANSPORTS, the message went out into etherx land, and
> Ahh! I implement it transport level with the knowledge that etherx (or
> whatever router we may be going through) may go through multiple servers!
> However, since Jabber is a transport level protocol, the tunnels between
> transports are ignored.
> etherx remains the same.
Ahh.. I've been looking at some application use of Etherx that would really
not use the Jabber protocol at all, and what I would like to see is a tag that
could be used interchangably eithin either the XML streams thru etherx, or the
Jabber protocol itself. It would also make it easier to transfer this data into
the message packet by the end transport, by simply copying the tags of the
stream into the tags of the message.
> > The transports will then need to ADD the routing data of the Stream to
> Only concerned about transport level, not router. I tried to make the
> language specific. Should I edit to make it more strong?
Not really 'more strong', but a slight modofication. Your specs also have a
'sent' and 'recieved' information, but I'd like to see a more dynamic tag, so we
could have 'stored', 'attemptedsend', 'archived', etc.. What about something
<id>Id of marker</id>
Of course, the use of tags versus attributes is up to opinion, and I just
started typing, so it's NOT the best way to handle it, but I hope you see what I
mean. This leads the route tag to be generic, and allow ANYTHING to leave a
timestamp, and not a transport tag. It also opens up the type field for each
timestamp, and not really a 'transport send and recieved' tag, but more generic.
<< Wanted: One decent sig >>
<< Preferably litle used >>
<< and stored in garage. ?>>
More information about the JDev