The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
May. 31, 2005
Filed:
Jun. 30, 2003
Steve C. Woods, Salmon Arm, CA;
Michael Mcguire, Salmon Arm, CA;
Harry Ogloff, Salmon Arm, CA;
Zvonimir Sko{hacek Over (C)}ić, Salmon Arm, CA;
Emeric Johnson, Salmon Arm, CA;
Steve C. Woods, Salmon Arm, CA;
Michael McGuire, Salmon Arm, CA;
Harry Ogloff, Salmon Arm, CA;
Zvonimir Sko{hacek over (c)}ić, Salmon Arm, CA;
Emeric Johnson, Salmon Arm, CA;
Coe Newnes/McGehee ULC, Salmon Arm, CA;
Abstract
A generic, scalable consumer subsystem/producer subsystem interface controller for exchanging data between at least one producer subsystem configured to produce a set of services characterized in a producer generated data set, and at least on consumer subsystem configured to consume the set of services, including an object-oriented producer application program interface configured for use on a multi-threaded, client-server operating system, wherein producer routines are configured to: initialize producer server objects maid producer client objects; receive requests for data from a consumer subsystem via the producer client objects; send acknowledgments to a consumer subsystem in response to requests from the consumer subsystem via the producer server objects; send data to a consumer subsystem in response to requests from the consumer subsystem via the producer server objects; and wherein consumer routines are configured to: initialize consumer server objects and consumer client objects; send requests for data to a producer subsystem via the consumer server objects; receive acknowledgments from a producer subsystem in response to requests from the producer subsystem via the consumer client objects; and, receive data from a producer subsystem in response to requests from the producer subsystem via the consumer client objects.