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

Computational Registry Services

IP.com Disclosure Number: IPCOM000131647D
Original Publication Date: 2005-Nov-11
Included in the Prior Art Database: 2005-Nov-11
Document File: 2 page(s) / 45K

Publishing Venue

IBM

Abstract

This publication describes a solution to add a service registry to a product where multiple third partys can supply computational components

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

Computational Registry Services

This publication describes a solution to add a service registry to a product where multiple third partys can supply computational components. These supplied components would be able to override the default computation of various selected run-time parameters (e.g. a random distribution function, calculations for window placement & configuration, encryption, algorithms, compression algorithms, security access controls, etc). The supplied services must be able to access other such services to provide composite functionality

    The product will provide a registry of services that can be provided by third parties. The services can be registered directly via APIs or indirectly by listing the services in a configuration file. The product will expose various run-time configuration points where a user enter requests which will be fulfilled by one (or more) of the registered services.

The following are the key elements of this solution:
1. The product must provide a registery of services that may be supplied by third parties. The services to be registered can be listed in a configuration file or some dialog in the product or other appropriate means.
2. The services to be registered must adhere to a protocol (e.g. it must implement a published Java interface).
3. The product must expose selected configuration points for user entry. (e.g. the user a select from a pre-defined list of algorithm or the user can enter a request to a service)
4. User entered requests are accepted as free-form text with no predefined syntax or sematics (these are determined by the individual services.themselves).
5. Multiple services can be registered and the order of registry in important - it establishes a precedence order from highest priority to lowest priority.
6. When the product is operational and it requires a result which is to be provided by a service request, the text of the request along with context information supplied by the product, is passed to the first service provider (the one with the highest priority) using the pre-established APIs (e.g. t...