Browse Prior Art Database

Dynamic Identification of Cached, Nested Resources

IP.com Disclosure Number: IPCOM000105342D
Original Publication Date: 1993-Jul-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 4 page(s) / 107K

Publishing Venue

IBM

Related People

Stone, DE: AUTHOR

Abstract

Cached Resources often contain dynamic information such as identifiers (IDs) of Nested Resources. These IDs can change within or between program communication sessions that use the resources. A method is disclosed for use within the Intelligent Printer Data Stream (IPDS*) to update the dynamic information automatically to allow reuse of the cached resources. This method allows a print driver program, such as Print Services Facilities (PSF) to maintain current state information within cached resources that contain transient attributes.

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

Dynamic Identification of Cached, Nested Resources

      Cached Resources often contain dynamic information such as
identifiers (IDs) of Nested Resources.  These IDs can change within
or between program communication sessions that use the resources.  A
method is disclosed for use within the Intelligent Printer Data
Stream (IPDS*) to update the dynamic information automatically to
allow reuse of the cached resources.  This method allows a print
driver program, such as Print Services Facilities (PSF) to maintain
current state information within cached resources that contain
transient attributes.

      IPDS, a patented IBM* data stream, provides many commands to
allow a host computer program to control the actions of a printer.
In an IPDS environment, page segment or overlay resources are cached
by Remote PrintManger (RPM) the first time that they are sent to an
RPM-connected printer.  These resources contain IPDS commands,
including commands that refer to (nest) other resources.  The IDs
within the commands that refer to the nested resources are only valid
during the current communication session and must be changed at each
subsequent session (Figure 1).

      When one resource object (resource A) is "included within" or
"mapped for invocation within" another resource (resource B),
resource A is said to be "nested" in resource B.  Both resource A and
resource B must be activated and identified by a Host-Assigned ID
(HAID) before resource B can be printed.

o   If resource A is a coded font, it is invoked within resource B
    via a local ID.  The local ID is mapped to the Resource A HAID
    via a Load Font Equivalence (LFE) command.  The LFE command can
    either be inside or outside of Resource B.
Resource A must have been previously activated and a HAID assigned
via a Load Font Control (LFC) command, a Load Symbol Set (LSS)
command, a Load Symbol Set (LSS) command, a Load Resource Equivalence
(LRE)/Request Resource List (XOA RRL) sequence, or a Load Font
Equivalence (LFE) command,  These commands, with the possible
exception of the LFE command, are not part of the nesting resource
(resource B).

o   If resource A is a page segment, it is invoked and the HAID is
    supplied in the Include Page Segment (IPS) command which becomes
    part of the nesting resource.  Resource A must have been
    previously activated and a HAID assigned via a Begin Page Segment
    command (for a downloaded page segment) or via an LRE/RRL
    sequence (for a resident page segment).

o   If resource A is an overlay, it is invoked and the HAID is
    supplied in the Include Overlay (IO) command which becomes...