Abstract: A remote messaging system for distributed computer system includes a client stub (217) and client and server remote messaging engines (209, 211). The client stub and the client remote messaging engine prepare a server-ready object, referred to as a RemoteMethodObject (219) in response to client application logic (207) requesting a service from server (227) in the form of a call to the stub. The object is of a type corresponding to a particular service, and includes a header identifying its type and a user requesting the service. The object further includes data parameters for the service. The object's type, once received by the server, is identified, and a “handle” operation called. The method for the handle operation is bound to the object based on its type. SystemObject manager (221) manages objects that are instances of classes registered with it. The SystemObject manager pre-allocates memory, and subdivides the memory into elements called SystemObjects.

Abstract: A method and apparatus for downloading large items packages the item as a plurality of packets and numbers each packet with an index stored in a header. For each user to whom an item is to be downloaded, a list of packets to be sent to the user is maintained. A send process loops through each user. In any given loop, one or more packets from the list is sent to the user. These packets are then marked as having been sent on that user's list. Only one download buffer for storing the download packets and only one network communications buffer for use by a network and a connectionless transport service is required to send the packets to a plurality of users on demand. Each user indicates which packets it did not receive and those packets are added back to that user's list for sending.