Browse Prior Art Database

Dynamic Update of Inbasket Triggered by X.400 Alerts

IP.com Disclosure Number: IPCOM000109809D
Original Publication Date: 1992-Sep-01
Included in the Prior Art Database: 2005-Mar-24
Document File: 1 page(s) / 40K

Publishing Venue

IBM

Related People

Bower, RA: AUTHOR [+3]

Abstract

This article describes a method for using the X.400 Alert in conjunction with the List abstract-operation to provide a means of giving dynamic updating of the inbasket list that is kept by the User Agent.

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

Dynamic Update of Inbasket Triggered by X.400 Alerts

       This article describes a method for using the X.400 Alert
in conjunction with the List abstract-operation to provide a means of
giving dynamic updating of the inbasket list that is kept by the User
Agent.

      X.400 is the international standard for electronic mail.  This
standard defines a Message Store (MS) and a User Agent (UA).  There
are several abstract operations that are used to communicate between
the MS and UA.  Two of these operations are:
     Alert: notify a user that new mail has arrived at the MS
     List : retrieve the inbasket for a user from the MS

      However, there is no method of using the Alert to give dynamic
update of the UA's inbasket list.

      When a UA first binds to a MS, it invokes a List operation to
get the list of mail items.  This list remains correct until the user
either receives a new mail item or deletes a current mail item.  If a
new mail item is received, the MS will issue an Alert operation that
informs the UA of the arrival of new mail.  In today's mail systems,
the user would have the UA issue a refresh command.  This command
results in a List operation being sent to the MS.  However, the UA
could use the contents of the alert to dynamically update the
inbasket list that it is keeping in local storage.

      This list would contain a flag to keep new mail items invisible
to the user until the refresh was issued.  When the user...