Network object frameworks

Details Network object frameworks Network object frameworks

1996-06-18

2001-06-19

Banankhah, Majid A. (Department: 2755)

Electrical computers and digital processing systems: multicomput

Computer-to-computer data routing

Least weight routing

C709S241000

Reexamination Certificate

active

06249821

ABSTRACT:

FIELD OF THE INVENTION
The present invention relates to creating a network application which accesses network services provided by a network operating system. More particularly, the present invention relates to a method for maintaining communication channels between network devices to allow state information and commands to be exchanged between the devices.
BACKGROUND OF THE INVENTION
Traditionally, network application access to network services and devices during application development is obtained by way of a software developer kit. As should be understood, the kit is generally distributed by the network operating system software vendor, and typically provides functional interfaces to a network Application Programmers Interface (API). The network API provides access to each of the network services, and also provides mechanisms to create communication channels to other network devices.
Network operating systems services include but are not limited to services provided by application servers, file servers, print servers and other network management tools. Typical management operations include user account management services, file and directory management services, volume services, queuing services, print management services, and connection information services, among other things.
File management services include opening, reading from, writing to, closing, archiving, protecting, encrypting, and otherwise managing files in a multiple user environment. Print management services include generating and maintaining printer definitions, form definitions, print service definitions, and queue connection definitions; pre- and post-filter processing; and print job redirection, among other things. Such services are typically divided into working segments to allow applications to access the services in a functional manner.
For an application to access a requested service, service-related information must be retrieved from a network database, and the retrieved information is employed to access one or more network devices that provides the requested service. Such information includes all the descriptive information about each service and identifiers for addressing the network devices and services directly. However, and as should be understood, such a process is cumbersome in that the retrieval of the information and the accessing of the service require multiple requests from the application, and in that the requests must be passed through circuitous routes.
A need exists, then, for a system and method for encapsulating network service-related information and network devices such that an application can virtually communicate directly with the appropriate network device or devices that provides the requested service. As should be understood, virtual communication refers to a logical communication process rather than a physically communication process.
Virtual communication between network-attached devices is made possible by creating channels, ports, or “sockets”, where each socket defines a logical connection between a first device and a second device. As should be understood by one skilled in the art, first and second devices connected by a socket can only communicate with each other by / through the socket. The same description holds true for software tasks which are communicating with each other through the network media. Tasks connected on a socket are guaranteed to send signals or messages to each other.
Messages are streams of data which are packetized in such a way that the message ends up at the right destination task and each end of the socket can decipher the information or data which is trying to be communicated. The packetized information contains identifiers and indexes which may change the state of the communication channel.
As one skilled in the art should recognize, object-oriented analysis and design (OOA&D) is an approach for classifying and describing interactions between object components, and then encapsulating and modeling such object components. Classifications are defined by generalizing object components. Object components are identified by recognizing characterizations and functions which behave as individual entities and have unique behavior and descriptive attributes. In the invention to be described below, a set of classifications, object components, and interactions between object components are defined. As seen in the drawings, the OOA&D for the present invention may be fully described though the use of classification and object component diagrams.
OOA&D object technology, object analysis, design theory, and terminology is discussed in detail in
Object
-
Oriented Analysis and Design with Applications,
Grady Booch, [Redwood City, Calif.: Benjamin/Cummings, 1993], hereby incorporated by reference. Because object designs build on each other (i.e. new objects are generally built from older objects), several class libraries are available for starting a new analysis and design. The object design of the present invention builds on the Rogue Wave Foundation Class Libraries, TOOLS.H++. As should be understood, TOOLS.H++ has classifications for objects such as strings, multi-byte strings, localized time and date, hash sets, binary trees, dictionaries, sorted lists, linked lists, etc.
The model-view-controller (MVC) architecture is a useful architectures used by OOA&D applications. The MVC is essentially a trinity of objects and classifications which facilitates the physical data collection (model), the expression or composition of the data presentation (view), and the interaction or interface between the presentation and the user or outside influence (controller).
Models are the physical data collection or content of the physical devices and the behavior or the devices as described by the system make up the objects. Each model keeps track of the raw data which may or may not be understandable to the user or outside influence. Views are the objects which interact directly with the models and whose primary purpose is to shape or present the model raw data. Each model may contain several view instances and each view may only exist for one model.
Each view instance may present the model in different ways or may only present sections or subsections or information about the model. The view can also write information into the model as raw data. In the implementation of the MVC, raw information is periodically collected by the model if at least one view exists for such model. A reference is registered with a model for every view created for the model. When a view is destroyed, the respective reference is released by the respective model.
The models and views are manipulated and processed with the actions of controller objects (also referred to as user interface objects). The controller objects cause methods of a view to be invoked which in turn may cause reactions in a related model. Accordingly, controller objects tend to cause the MVC architecture to be highly event-driven. Therefore, event-driven operating systems such as the MICROSOFT WINDOWS operating system from MICROSOFT Corporation allow for a clean existence of an MVC architecture.
SUMMARY OF THE INVENTION
Briefly stated, in the preferred embodiment of the present invention, a computer network includes at least one network client memory, a network operating system executing in the network client memory for operating the computer network and for providing access to network services, and a network application executing in the network client memory for performing an application function. The computer network also has a plurality of network devices interfaced to the network operating system and available to the network application and the network operating system for performing the network services.
Each network device provides at least one specific network service and has an object component in the network client memory representative of the network device. Each object component includes an interface such that the network application is in direct communication with the interface of each ob

Affiliated with

Also associated with

Rating

Network object frameworks does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Network object frameworks, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Network object frameworks will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-2533143