Appeal 2007-0226
Application 09/823,866
(Final Rejection 2). This statement seems to say that the Examiner considers
a "client" and "server" to be "objects," instead of functions and procedures
on the client and server. However, since Schmidt describes "wrapper
facades" whose purpose is "to encapsulate low-level functions and data
structures with object-oriented (OO) class interfaces" (Schmidt, p. 1 under
"Introduction") for use in networking applications (Schmidt, p. 3 under
"Problem" and "Solution"), i.e., encapsulation of objects, we interpret the
rejection, in context, to be that the "wrapper facade" in Schmidt provides
access to objects on the clients and server in the networking environment.
The Examiner continues by finding that Schmidt teaches "means for
identifying at least two objects (one being the client and one being
database/printer service) from a plurality of objects (client, database, printer,
console services/functions) to communicate (invoke/request service)
[fig.s [sic] 1, 3" (Final Rejection 2). Again, while this seems to say that the
physical objects of client computer, database, printer, and console in
Figure 1 are "objects," in the context of Schmidt, we interpret the rejection
to be that "objects," in the sense of functions or procedures, on the client
computer, database, printer, etc. in Figure 1 are in communication.
The Examiner further finds that Schmidt "means for locating the at
least two objects to communicate (socket handles) [page 1, right col.; page 6,
right col., 2nd code listing" (Final Rejection 2). The two objects (one on the
client and one on the server) communicate via "socket handles" which are
ports at a certain IP address.
5
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Next
Last modified: September 9, 2013