OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Refiedn Proposal on Group Timing Parameters and Termination Conditions




My refined proposal for Group Termination Conditions:

        For all incoming messages in a group, the receiver checks the 
expiry time of incoming messages, and if not expired, uses the value to 
update a running statistic for the MaxExpiryTimeOfMessagesReceivedInGroup

        The reliable message MAY contain an optional attributes, 
GroupExpiryTime of GroupId.  Presence of GroupExpiryTime indicates a 
fixed duration group.   All messages in group MUST have expiryTime less 
or equal to GroupExpiryTime

        The reliable message MAY contain an optional attribute 
GroupMaxIdleDuration, of GroupId. Presence of GroupMaxIdleDuration 
indicates another condition to terminate group. If the receiver detects 
that no message for that group has been received for an interval of time 
equal to the GroupMaxIdleDuration, the group will be terminated

        Neither of the two optional attributes of GroupId are allowed 
to be present in singleton groups

        If neither GroupExpiryTime nor GroupMaxIdleDuration is present 
as attributes of GroupId, then the expiryTime of the highest sequenceNo 
sent for that group must be greater or equal to the expiryTime of all 
previous messages in the group.  For such a group, the receiver RMP 
MUST  use the MaxExpiryTimeOfMessagesReceivedInGroup as the 
effectiveGroupExpiryTime for that group.

        The presence and values of both attributes of GroupId must be 
identical for every message sent in the group.

        If both timing attributes are present, the first criteria that 
fires terminates the group.

        Presence of status=end always takes precedence to signal 
termination of a group.

        When a group is terminated for any of the four reasons 
(status=end, reach GroupExpiryTime, GroupMaxIdleDuration passes without 
a received message, reach effectiveGroupExpiryTime) , all messages and 
group state information are held until the GroupExpiryTime if it is 
present, or until the MaxExpiryTimeOfMessagesReceivedInGroup if the 
GroupExpiryTime is not present.


Processing order constraints must be clarified, if we can agree to the 



Tom Rutt		email: tom@coastin.com; trutt@fsw.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]