Electrical computers and digital data processing systems: input/ – Input/output data processing – Data transfer specifying
Reexamination Certificate
1999-01-20
2003-05-13
Shin, Christopher B. (Department: 2182)
Electrical computers and digital data processing systems: input/
Input/output data processing
Data transfer specifying
C710S003000, C709S203000, C709S227000, C709S230000, C709S241000, C709S241000
Reexamination Certificate
active
06564270
ABSTRACT:
COPYRIGHT NOTIFICATION
Portions of this patent application contain materials that are subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
FIELD OF THE INVENTION
This invention generally relates to improvements in computer systems, and more particularly to a system and method for service creation in an object-oriented operating system.
BACKGROUND OF THE INVENTION
Computer systems in general are very rigid. Application developers and users of the system must often know intimate details of hardware protocol and configurations to provide a system in which information flows smoothly. Details of each particular type of port and IO device must be dealt with on an individual basis. Application developers and users must also be kept constantly abreast of each change in the system in order to provide corresponding changes to the software and hardware so that the changes can be fully exploited.
The rate at which IO devices change, as well as the rate of change of intermediate elements used to transfer information to and from an IO device, is extremely fast. Each change requires a learning process of system users so that the system may be kept performing in an optimum manner.
A computer system can be thought of as a large collection of clients which need services performed. Clients could be considered to be virtually any part of the system which may need something. For example, the CPU could be considered to be a client that needs a service performed by a particular element in the system. The performance of the service may involve many steps, and many elements to provide the requested service. A service could be considered to be anything that provides something needed by another entity in the system. For example, a particular chip may provide a particular type of digital signal processing as a service for another system element. A single element could at one time be a client, and at another time provide a service to a client.
The interplay of clients and services often requires great attention by, developers and users to make the requests for services, and provision of services, a smooth process. The protocol for services requests and provision is often very inflexible, and requires intervention in minute details to change the protocol. In many respects, requests for services and providing services could be considered to be set in stone.
There is therefore, a need to provide a flexible system for requesting and providing services. The system needs to overcome the above difficulties concerning the level of detail involved, the problems associated with system changes, and the overall rigidity of software and hardware between clients and service providers.
SUMMARY OF THE INVENTION
Accordingly, it is a primary object of the present invention to provide a system and method for improving the interaction between clients and services.
It is another object of the present invention to provide a system and method for improving the flexibility in adjusting to changes in a system of clients and service providers.
It is vet another object of the present invention to provide a system and method for allowing requests for services without concern for details of the service requested.
It is another object of the present invention to provide a system and method for allowing requests for services without concern for details of the service provider.
These and other objects are realized by an interface framework that creates services in response to a request. The system receives an interface reference, and from the reference creates a previously nonexistent service. The interface reference creates in interface maker, which performs the actual creation and activation of a requested service. Activation of the service can be thought of as a two step process in which a service stack description is created, and from this description a service stack is created.
The interface reference is an entity that encapsulates all information necessary to create a service. The client has the interface reference, and activates the reference to create the service needed. The interface reference first creates a service stack description by determining the service interfaces making up the top and bottom of the service stack, and then searching to find a set of services between the top and bottom interfaces that will form the required service stack. The interface maker serves the purpose of “buffering” service provider classes from the service stack framework.
From the service stack description, interface makers corresponding to the stack description are created. This creation occurs from the bottom of the description up. The service stack description can be thought of as a list of references to interface makers.
REFERENCES:
patent: 4407016 (1983-09-01), Bayliss et al.
patent: 4530052 (1985-07-01), King et al.
patent: 4597044 (1986-06-01), Circello
patent: 4821220 (1989-04-01), Duisberg
patent: 4885717 (1989-12-01), Beck et al.
patent: 4891630 (1990-01-01), Friedman et al.
patent: 4953080 (1990-08-01), Dysart et al.
patent: 5041992 (1991-08-01), Cunningham et al.
patent: 5050090 (1991-09-01), Golub et al.
patent: 5060276 (1991-10-01), Morris et al.
patent: 5075847 (1991-12-01), Fromme
patent: 5075848 (1991-12-01), Lai et al.
patent: 5093914 (1992-03-01), Coplien et al.
patent: 5119475 (1992-06-01), Smith et al.
patent: 5125091 (1992-06-01), Staas, Jr. et al.
patent: 5129084 (1992-07-01), Kelly, Jr. et al.
patent: 5133075 (1992-07-01), Risch
patent: 5136705 (1992-08-01), Stubbs et al.
patent: 5151987 (1992-09-01), Abraham et al.
patent: 5181162 (1993-01-01), Smith et al.
patent: 5212787 (1993-05-01), Baker et al.
patent: 5226117 (1993-07-01), Miklos
patent: 5257369 (1993-10-01), Skeen et al.
patent: 5265239 (1993-11-01), Ardolino
patent: 5297283 (1994-03-01), Kelly, Jr. et al.
patent: 5297284 (1994-03-01), Jones et al.
patent: 5315703 (1994-05-01), Matheny et al.
patent: 5317741 (1994-05-01), Schwanke
patent: 5325533 (1994-06-01), McInerney et al.
patent: 5327562 (1994-07-01), Adcock
patent: 5333319 (1994-07-01), Silen
patent: 5339430 (1994-08-01), Lundin et al.
patent: 5339438 (1994-08-01), Conner et al.
patent: 5341477 (1994-08-01), Pitkin et al.
patent: 5369770 (1994-11-01), Thomason et al.
patent: 5421016 (1995-05-01), Conner et al.
patent: 5423023 (1995-06-01), Batch et al.
patent: 5428792 (1995-06-01), Conner et al.
patent: 5432925 (1995-07-01), Abraham et al.
patent: 5437027 (1995-07-01), Bannon et al.
patent: 5903754 (1999-05-01), Pearson
patent: 6134594 (2000-10-01), Helland et al.
patent: 6223217 (2001-04-01), Pettus
patent: 501610 (1992-09-01), None
Proc. 2ndInt'l Workshop on Object Orientation in Operation Systems 24, 9/92, France, pp. 212-220, Dave et al. “Proxies, Application Interfaces, and Distributed Systems”.
Distributed Systems Engineering, V.1 (2), 12/93, UK, pp. 112-125, Schill et al. “DC++: Distributed Object Oriented System Support on Top of OSF, DCE”.
Dumas, Joseph and Paige Parsons. “Discovering the Way Programmers Think: New Programming Environments.”Communications of the ACM. Jun. 1995: pp. 45-56.
Pascoe, Geoffrey A. “Encapsulators: A New Software Paradigm in Smalltalk-80.” OOPSLA '86 Proceedings, Sep. 1986: pp. 341-346.
Purtilo, James M. and Joanne M. Atlee. “Module Reuse by Interface Adapations.”Software-Practice and Experience. Jun. 1991: pp. 539-555.
Lam, Siman S. “Protocol Conversion.”IEEE Transactions on Software Engineering, Mar. 1988: pp. 353-362.
Thatte, Satish R. “Automated Synthesis of Interface Adaptors for Reuseable Classes.”POPL '94.Jan. 1994: pp. 174-187.
Yellin, Daniel M. and Robert E. Strom. “Interfaces, Protocols, and the Semi-Automatic Construction of Software Adaptors,”OOPSLA '94.Oct. 1994: pp. 176-190.
Jacobson, Ivar and Fredrick Lindstrom. “Re-engineering of old systems to an object-oriented architecture.”OOPSLA '91:
Andert Glenn P.
Norman George William
Doudnikoff Gregory M.
Kudirka & Jobse LLP
Perveen Rehana
Shin Christopher B.
LandOfFree
Isolating client application requests for device services... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Isolating client application requests for device services..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Isolating client application requests for device services... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3059374