Method, computer program product, and data structure for validating creation of and routing messages to file object

Claim 2

In a computer operating system that includes a) a driver object for managing a software driver as a system resource, b) one or more device objects each of which define a software driver's functionality and availability to other operating system resources and each of which includes a private data area containing a validation table with valid file object types and associated create handlers for each file object type, and c) one or more file objects for managing invocation of an operating system resource as specified by a particular device object and each of which includes a private data area containing an IRP request handler table and a validation table with valid file object types and associated create handlers for each file object type, and wherein the file objects are hierarchically related to parent objects that may consist of either device objects or other file objects, a method of standardizing i) validation of creation of, or ii) routing of messages, to file objects in order to eliminate the need for third party driver developers to write validation or routing code for such drivers, the method comprising steps for: receiving at a driver object a request to either create a particular type of file object or to route a message to a particular type of file object; sending the received request to a multiplexing dispatch function which is resident as part of the operating system, as opposed to being provided by a third party driver developer; the multiplexing dispatch function then accessing a private data area of a parent object for the purpose of searching for said particular type of file object for which the creation or routing request was sent; and if said particular type of file object is found, accessing the appropriate create handler for said particular type of file object, and if not, returning an error message and rejecting the request.

Claim 3

A method as recited in claim 1 wherein the request received at the driver object includes the information needed to determine if the parent object is a file object or a device object.

Claim 4

A method as recited in claim 1 wherein the request received at the driver object is implemented as a data structure.

Claim 5

A method as recited in claim 1 wherein the multiplexing dispatch function determines whether the parent object is a file object or a device object.

Claim 6

A method as recited in claim 1 wherein the multiplexing dispatch function is a single function which processes IRP requests.

Claim 7

A method as recited in claim 1 wherein the multiplexing dispatch function is one of several multiplexing functions germane to the particular request received by the driver object.

Claim 8

A method as recited in claim 3 wherein the data structure includes a handle to the parent object (our spec only indicates handle passes for parent file object but it would have to for either).

Claim 9

A method as recited in claim 4 wherein if the parent object is a file object, the multiplexing dispatch function uses the private data area of the parent file object to reference an IRP request handler table.

Claim 10

A method as recited in claim 1 wherein if the parent object is a device object, the multiplexing dispatch function uses the private data area of the parent device object to reference a validation table.

Claim 11

A method as recited in claim 8 wherein if the request is a creation request, the multiplexing function access a validation table referenced in the IRP request handler table.

Claim 12

A method as recited in claim 1 wherein the multiplexing function compares a string in the request to create a particular type of file object with file object type string contained in the validation table.

Claim 13

A method as recited in claim 10 wherein the multiplexing function compares a string in the request to create a particular file object with file object type strings contained in the validation table.

Claim 14

A method as recited in claim 10 wherein the multiplexing function compares an index value in the request to create a particular type of file object with a range of permissible index values contained in the validation table.

Claim 15

A method as recited in claim 1 wherein the multiplexing function compares an index value in the request to create a particular type of file object with a range of permissible index values contained in the validation table.

Claim 16

In a computer operating system that includes a) a driver object for managing a software driver as a system resource, b) one or more device objects each of which define a software driver's functionality and availability to other operating system resources and each of which includes a private data area containing a validation table with valid file object types and associated create handlers for each file object type, and c) one or more file objects for managing invocation of an operating system resource as specified by a particular device object and each of which includes a private data area containing an IRP request handler table and a validation table with valid file object types and associated create handlers for each file object type, and wherein the file objects are hierarchically related to parent objects that may consist of either device objects or other file objects, a computer program product for implementing a method of standardizing i) validation of creation of, or ii) routing of messages to, file objects in order to eliminate the need for third party driver developers to write validation or routing code for such drivers, the computer program product comprising: a computer readable medium for carrying computer program code means for implementing said method, and wherein said method is comprised of the steps for; receiving at a driver object a request to either create a particular type of file object or to route a message to a particular type of file object; sending the received request to a multiplexing dispatch function which is resident as part of the operating system, as opposed to being provided by a third party driver developer; the multiplexing dispatch function then accessing a private data area of a parent object for the purpose of searching for said particular type or file object for which the creation or routing request was sent; and if said particular type of file object is found, accessing the appropriate create handler for said particular type of file object, and if not, returning an error message and disregarding the request.

Claim 17

In a computer operating system that includes a) a driver object for managing a software driver as a system resource, b) one or more device objects each of which define a software driver's functionality and availability to other operating system resources and each of which includes a private data area containing a validation table with valid file object types and associated create handlers for each file object type, and c) one or more file objects for managing invocation of an operating system resource as specified by a particular device object and each of which includes a private data area containing an IRP request handler table and a validation table with valid file object types and associated create handlers for each file object type, and wherein the file objects are hierarchically related to parent objects that may consist of either device objects or other file objects, a computer program product for implementing a method of standardizing i) validation of creation of, or ii) routing of messages to, file objects in order to eliminate the need for third party driver developers to write validation or routing code for such drivers, the computer program product comprising: a computer readable medium for carrying computer program code means for implementing said method, and wherein said method is comprised of the steps for; receiving at a driver object a request to either create a particular type of file object or to route a message to a particular type of file object; sending the received request to a multiplexing dispatch function which is resident as part of the operating system, as opposed to being provided by a third party driver developer; the multiplexing dispatch function then accessing a private data area of a parent object for the purpose of searching for said particular type or file object for which the creation or routing request was sent; and if said particular type of file object is found, accessing the appropriate create handler for said particular type of file object, and if not, returning an error message and disregarding the request.

Claim 18

A computer program product for implementing the method as recited in claim 15 wherein the request received at the driver object includes the information needed to determine if the parent object is a file object or a device object.

Claim 19

A computer program product for implementing the method as recited in claim 15, wherein the request received at the driver object is implemented as a data structure.

Claim 20

A computer program product for implementing the method as recited in claim 15 wherein the multiplexing dispatch function determines whether the parent object is a file object or a device object.

Claim 21

A computer program product for implementing the method as recited in claim 15 wherein the implementing dispatch function is a single function which processes IRP requests.

Claim 22

A computer program product for implementing the method as recited in claim 15 wherein the multiplexing dispatch function is one of several multiplexing functions germane to the particular request received by the driver object.

Claim 23

A computer program product for implementing the method as recited in claim 17 wherein the data structure includes a handle to the parent object (our spec only indicates handle passes for parent file object but it would have to for either).

Claim 24

A computer program product for implementing the method as recited in claim 18 wherein it the parent object is a file object, the multiplexing dispatch function uses the private data area of the parent file object to reference an IRP request handler table.

Claim 25

A computer program product for implementing the method as recited in claim 18 wherein if the parent object is a device object, the multiplexing dispatch function uses the private data area of the parent device object to reference a validation table.

Claim 26

A computer program product for implementing the method as recited in claim 22 wherein if the request is a creation request, the multiplexing function access a validation table referenced in the IRP request handler table.

Claim 27

A computer program product for implementing the method as recited in claim 23 wherein the multiplexing function compares a string in the request to create a particular type of file object with file object type strings contained in the validation table.

Claim 28

A computer program product for implementing the method as recited in claim 23 wherein the multiplexing function compares an index value in the request to create a particular type of file object with a range of permissible index values contained in the validation table.

Claim 29

A computer program product for implementing the method as recited in claim 24 wherein the multiplexing function compares a string in the request to create a particular type of file object with file object type strings contained in the validation table.

Claim 30

A computer program product for implementing the method as recited in claim 24 wherein the multiplexing function compares an index value in the request to create a particular type of file object with a range of permissible index values contained in the validation table.