Appeal 2007-0226
Application 09/823,866
ll. 19-23). If the client on the local host desires some data on a remote host,
the client sends a request for service to a server process on a remote host, the
server accepts the request and conveys it to a database service, the server
retrieves the response from the database service on the remote host and
returns the response to the requesting client (col. 6, ll. 24-39). The "local
host" may be a "local multi-user system" (col. 4, ll. 9-10). A client is a
process which issues requests (col. 7, ll.33-34). A "server" is an
intermediary between a client and a service (col. 7, ll. 35-36), such as
between the Human Interface Server between a Remote Object Client and a
Human Interface Service and a Starter Server between a Starter Client and a
Starter Service, as shown in Figure 2. The local host and remote hosts can
be at different locations (col. 8, 21-56).
Analysis
Claim 1 is extremely broad and essentially recites a system for
enabling two objects at different server locations (not necessarily different
servers) to communicate. The term "object" is a broad term that is not
expressly defined in the Specification, except loosely that the "objects are
for the most part, similar to everyday functions or procedures" (Specification
10, ll. 9-10). Thus, an object could be any program and is not limited to a
"class" in an objected-oriented programming language. "Server" is also not
defined. We presume Appellants intend the conventional meaning of server
as a computer system in a network that is shared by multiple users. Since
server-to-server communication is notoriously well known in the Internet
9
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Next
Last modified: September 9, 2013