Browse Prior Art Database

Method and Apparatus for HTTP Publish of Web-Site File and Meta-Data Disclosure Number: IPCOM000010729D
Original Publication Date: 2003-Jan-15
Included in the Prior Art Database: 2003-Jan-15
Document File: 4 page(s) / 66K

Publishing Venue


This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 4

Method and Apparatus for HTTP Publish of Web-Site File and Meta-Data

  Web content management solutions include the ability to publish managed files and other content to a runtime web server. This paper describes a method of publishing content (files and other content referred collectively here as resources) using HyperText Transfer Protocol (HTTP). Resources are sent from the authoring server to a runtime server running IBM WebSphere or another Application Server capable of receiving HTTP PUT requests as a servlet does.

Most web-site publishing mechanisms use the file-transfer protocol (FTP) for sending completed files to the staging or production web-site. This mechanism includes many limitations since there is no servlet-like architecture to receive the FTP request and perform any special processing based on the data or the request sent. Using an application server, an HTTP servlet can be designed to receive data and info and do any special processing like updating a database, calling an edge-server API, etc.

With this architecture the following publish features are possible by implementing sophisticated targets:
transactional publish where a set of data sent individually but as part of a larger transaction
replication where files and data are sent to many servers
chaining where a publish target can in turn publish to another target (for mirroring purposes perhaps)

The Publish function of the authoring server is a symbiotic relationship with the publish target servlet. One example of this is transactional publish. The authoring server publish provides a unique key for all communications with the target servlet over the set of publish data but the servlet itself must implement the transactional mechanism itself.

A set of data is published to a server on a resource collection basis using the following mechanism:


Page 2 of 4









The same transaction id value is used for all resources for a particular server. This way, transactional processing may be performed by the target servlet on any scope level up to and including the entire publish data set.

The request 1 described above includes an XML stream containing the ids or the resource collection which the authoring server intends to send. The response at 2 is an XML stream in the same format though only the <resourceId> tags are required. An empty request would include on the resource-type tag.


Initiate transaction with target by sending the transaction Id. Includes negotiation of

datastream capabilities (e.g. compressed data) Response to transaction start request. Includes response to capabilities info.

The first request notifies the server a publish transaction is starting for a particular

resource collection. The request includes a list of ids and meta data (in XML format) which the a...