Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Extending the Notebook Paradigm to Accommodate for Distributed Data Environments

IP.com Disclosure Number: IPCOM000114665D
Original Publication Date: 1995-Jan-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 2 page(s) / 55K

Publishing Venue

IBM

Related People

Pl Banda, V: AUTHOR [+4]

Abstract

In the Workplace Shell implementation of the notebook, all data on the pages is saved as each control is manipulated. This forces a condition where all data is expected to be saved immediately as the users interacts with the controls. In a distributed data environment, where data is to be stored remotely, this type of design would unnecessarily congest the network with minute packets of data to try to maintain this same paradigm.

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

Extending the Notebook Paradigm to Accommodate for Distributed Data
Environments

      In the Workplace Shell implementation of the notebook, all data
on the pages is saved as each control is manipulated.  This forces a
condition where all data is expected to be saved immediately as the
users interacts with the controls.  In a distributed data
environment, where data is to be stored remotely, this type of design
would unnecessarily congest the network with minute packets of data
to try to maintain this same paradigm.

      Disclosed is a solution to this problem by treating the entire
notebook as a single object, and the saving of its data the same way,
as one chunk.  The solution is to treat the notebook view (Settings)
exactly as any other view of the object.  In other words, this view
as a whole, represents the object; therefore, data storage occurs by
saving the object also.

      This means all data pertaining to the object is not collected
and sent out over the network to be stored until the user makes a
conscious decision to commit the data.  To enable this requires
providing a means for the user to act upon the notebook as a whole or
in pieces, depending upon their needs.  Providing a set of
pushbuttons outside of the notebook pages in the notebook itself
solves this problem.  The necessary pushbuttons are: Set, Apply,
Reset, Cancel and Help.  They are defined as follows:
  Set -  Saves all data and closes the notebook.  This is also the
  ...