org.tickertape.message 3x - Thread-Id

I-Wanicki, Martin martin.wanicki at boeing.com
Mon Aug 26 10:59:51 EST 2002


Suggest change to the following description in spec

 Thread-Id   string     When sending a message to a group to which
                        the sender is not subscribed, but wishes
                        to see any replies, this field should be
                        set (and the sender's user agent should
                        alter its subscription so as to receive
                        any messages with this Thread-Id value).

                        User agents, receiving a message with a
                        Thread-Id set, SHOULD copy the supplied
                        value into the same-named attribute of any
                        reply messages.

                        This value must be globally unique.  See
                        Message-Id for recommendations.


This description does not seem to suggest the use of this field

The notion of thread-based manipulations like, but not limited to
thread blocking is not mentioned - as such since these types of
manipulations seem to be becoming part of a few clients, interoperability
would almost demand this field to be set at all times.

The ides of use seems to be
	New 'ROOT' messages are the beginning of a new thread
	therefor its would seem to be legal to set the Thread-Id to the
Message-Id
	of the new outgoing message.
	Since it is mandatory to copy the incoming Thread-id to the outgoing
	Thread-Id in all reply messages I suggest this field become
mandatory
	for tickertape messages.


here's my suggestion ...

 Thread-Id   string     This field should be populated at all times

                        User agents, receiving a message with a
                        Thread-Id set, SHOULD copy the supplied
                        value into the same-named attribute of any
                        reply messages.

                        User agents, sending a new message which is
				NOT a reply, SHOULD copy the Message-Id 
				from the notification about to be sent 
				into the same-named attribute of the 
				notification about to be sent.

                        When sending a message to a group to which
                        the sender is not subscribed, but wishes
                        to see any replies, this field should be
                        set (and the sender's user agent should
                        alter its subscription so as to receive
                        any messages with this Thread-Id value).

                        This value must be globally unique.  See
                        Message-Id for recommendations.



Over to the ticker-dev(otee's)

Cheers


martin





More information about the ticker-dev mailing list