International Business Machines Corporation

John Christopher Ripstra

George James Romano

Eric Nels Herness

Eric Howland Jenney

Frank William Gilchrist

Jeffrey John Parker

David L Johnson

Dennis Steven DeLorme

Michael Lawrence Nordstrom

Alan Leon Levering

Multiple links to the same object are managed by storing the attributes of the object in only one place. Each directory which links to the object has an object attribute table; each table has a number of entries all capable of storing the attributes of the files linked to the directory. One of the entries in a directory linked to a file stores the attributes of that file, called the master entry; other entries in the same or other directories that also link to the same file have slave entries capable of storing the attributes but not storing the attributes in their respective object attribute table. The file need only address the master entry. The master entry may point to the other slave entries which may point back to the master or to other slave entries as determined by a pointer protocol. When the master entry is to be deallocated, another of the qualified slave entries receives the attribute information and the file is updated to reflect that a new master has been declared. According to the pointer protocol, other slave entries may also be updated.

Management of multiple links to a file in a file system

Synchronization software in a computer operating system evaluates with respect to an exposure goal the ages of byte stream files queued for synchronization, and dynamically adjusts synchronization (&ldquo;sync&rdquo;) capacity in response to the evaluation. The synchronization of byte stream files occurs at rates responsive to the sync capacity. Several parameters are used to adjust sync capacity: a lead time, the number of active sync tasks, and the priority of the sync tasks. These parameters are adjusted in a manner to impact system performance to the least extent possible.

Adaptive, time-based synchronization mechanism for an integrated posix file system

A framework for use with object-oriented programming systems provides a common message processing system structure that can be placed on any OOP platform and be configured to support any e-mail message protocol standard or specific mail server function. The framework defines an e-mail message as a number of distinct objects, each of which contains information that describes some portion of the message. All messages received by a system in which the framework is implemented are defined on this core object structure. Another set of objects and methods define the processing steps required for a mail server to process a message. A message is received as a class of message objects, which are assigned a message type that determines the subsequent processing steps to which the message object is subjected. As a message is processed, the objects of which it is comprised are changed, so that the message processing can be interrupted and then resumed without loss or duplication of processing steps.

Object oriented mail server framework mechanism

Growing community of inventors

Rochester, MN, United States of America

John Christopher Ripstra