Skip to main content

Fixed Content Storage (FCS) Application Programming Interface (API)
draft-canessa-fcs-api-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Author John Canessa
Last updated 2003-05-21
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

During the past twelve months there has been interest in Fixed Content Storage servers. Vendors have been introducing offerings that use proprietary API calls. This is causing delay in acceptance. By using a set of standard API calls software developers, vendors and end-users would benefit. This document provides background on the need for an API. It defines a simple and reduced yet robust set of Application Programming Interface (API) calls to be supported by implementations of FCS servers. Store, query and retrieve operations are described in detail. The concept, description and format of a Global Unique Identifier (GUID) are provided. A GUID serves as a unique handle to each object stored by a FCS server. The list of the set of API calls is defined. A basic set of data structures and support functions is presented.

Authors

John Canessa

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)