Appeal No. 96-3301
Application 08/176,603
something. These can then be treated as a package which can be
manipulated in various ways. Objects may represent hardware such
as CPUs, memory, printers, disks, tape drives, and other devices;
software entities such as programs, files, and semaphores; and
various other entities. While a "user interface environment" can
be treated as an object, not all objects are a user interface
environment. The examiner does not point to where Davidson
discloses an object corresponding to the claimed "user interface
environment" that displays "a user interface on a display that is
connected to said computer." The examiner seems to equate the
server object in Davidson with the "user interface environment"
and the client object with the object in step a of claim 1.
However, the server object for handling a remote procedure call
has not been demonstrated by the examiner to be part of a user
interface environment. The example in Davidson of a daemon
process for handling a shared resource, such as a printer, has no
need to access the user interface environment in order to perform
the printing function. Davidson deals with remote procedure
calls in a distributed computer system and the examiner has not
offered any explanation of why a computer would need to access a
function in the user interface of another computer. The
examiner's statement that Davidson describes an "environment
where a (client) object may access (interface) another object
- 6 -
Page: Previous 1 2 3 4 5 6 7 8 9 10 Next
Last modified: November 3, 2007