Browse Prior Art Database

Method for Managing Distribution Navigation Life Utilizing User Constraint

IP.com Disclosure Number: IPCOM000111577D
Original Publication Date: 1994-Mar-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 92K

Publishing Venue

IBM

Related People

Johnson, WJ: AUTHOR [+2]

Abstract

Provided is a user-constraint parameter to a persistent acknowledgement. Further provided is the underlying services for implementing the parameter.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Method for Managing Distribution Navigation Life Utilizing User Constraint

      Provided is a user-constraint parameter to a persistent
acknowledgement.  Further provided is the underlying services for
implementing the parameter.

      Prior art has shown a method for sending a mail distribution
with a special type of acknowledgement option which allowed showing
the originator all recipients of the item, including downstream
recipients.  As a mail item propagated throughout a network as the
result of recipients sending to their recipients, the originator is
made aware of all people who receive the mail item.  In fact, the
tree structure of who sent to whom is built and managed over time
throughout the life of the distribution and subsequent sends of that
distribution from and to downstream recipients.  The tree may be
interesting for a specified time.  The user needs a method for
limiting the growth of the acknowledgement tree to only those
recipients the user is interested in.

      For example, a user sends a mail item to one or more users and
sets the persistent acknowledgement option so all users who receive
the item will be known to the originator in a tree-like fashion
describing who sent to whom.  This article allows the user to specify
a user constraint for which the acknowledgements will continue to be
logged in the tree.

      Various embodiments exist for specifying the user constraint:

o   Number of total recipients for which to manage status for (when
    maximum is reached, no more status is logged in the tree)

o   Number of total node names for which to manage status for (when
    maximum is reached, no more status is logged in the tree; user
    only interested in how many nodes involved)

o   Number of total system names for which to manage status for (when
    maximum is reached, no more status is logged in the tree; user
    only interested in how many systems involved)

o   Wildcard of recipient user names for which will participate in
    having status logged

o   Wildcard of recipient node names for which will participate in
    having status logged

o   Wildcard of recipient system names for which will participate in
    having status logged

o   Wildcard of recipient system group names for which will
    participate in having status logged

      An arbitrary user constraint and format may be implemented
without departing from the spirit and scope of the article.  The
acknowledgements continue to be manage...