Browse Prior Art Database

Autonomic Combination of User Input and Policies to Drive Ordering of Protocol Layers

IP.com Disclosure Number: IPCOM000033512D
Original Publication Date: 2004-Dec-13
Included in the Prior Art Database: 2004-Dec-13
Document File: 3 page(s) / 81K

Publishing Venue

IBM

Abstract

The invention is a policy driven mechanism to drive the ordering of linking multiple object oriented layers. The usage of this mechanism is to enhance the ability to link together multiple protocol layers in a way that is most optimal and requires the least amount of input from the user.

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 66% of the total text.

Page 1 of 3

Autonomic Combination of User Input and Policies to Drive Ordering of Protocol Layers

The ordering of independent pieces of code in order to create a fully functional system is complex. Often, only the authors of those pieces of code know how they should fit properly into a system. This independent ordering of new functional components in protocol stacks has been nearly impossible considering the amount of user knowledge needed in order to achieve such a task.

With a componentized protocol stack where each protocol layer is represented by a logical object oriented grouping of code, understanding the system and each independent layer can be quite difficult. It becomes more complex when multiple layers can exist on top of one another. For example:

TCP

TCP

Web Serving

Web Serving

HTTP

HTTP

Compression

Compression

SSL

SSL

TCP

TCP

Web Serving

Web Serving

HTTP

HTTP

SSL

SSL

Compression

Compression

1

[This page contains 1 picture or other non-text object]

Page 2 of 3

Web Serving

Web Serving

Web Serving

Web Serving

HTTP

HTTP

Web Serving

Web Serving

HTTP

HTTP

Compression

Compression

HTTP

HTTP

SSL

SSL

SSL

SSL

TCP

TCP

TCP

TCP

TCP

TCP

Additionally, to further ensure that the stacks are coherent, the policies define the interface it expects to receive from the layer directly below it and what it plans to expose to the layers above it. This helps ensure the stacks work and are coherent upon creation.

Here is a sample flow as to how these layers may be autonomically put together...