Abstract: A method includes receiving, from a remote computing device, an update request, the update request including a first signature corresponding to a client-side application package that is stored at the remote computing device. The method also includes identifying a first server-side application package using the first signature. The method also includes generating a differential update package using the first server-side application package and a second server-side application package as inputs, wherein the differential update package, when applied to the client side application package, is operable to modify to the client-side application package such that it is functionally equivalent to the second server-side application package.

Abstract: A method includes transmitting, from a computing device to one or more server computers, an update request corresponding to a client-side application package that is stored at the computing device. The client side application package contains a plurality of application components. The method also includes receiving a differential update package in response to the request. The differential update package includes a plurality of deltas, wherein each delta corresponds to one of the application components contained in the client side application package. The method also includes applying the plurality of deltas to modify at least some of the application components from the plurality of application components.

Abstract: A method includes receiving, from a remote computing device, an update request, the update request including a first signature corresponding to a client-side application package that is stored at the remote computing device. The method also includes identifying a first server-side application package using the first signature. The method also includes generating a differential update package using the first server-side application package and a second server-side application package as inputs, wherein the differential update package, when applied to the client side application package, is operable to modify to the client-side application package such that it is functionally equivalent to the second server-side application package.

Abstract: A method and apparatus for publishing and receiving events to a network. A plurality of "publisher" entities publish information and a plurality of "subscriber" entities request and use the information. Publishers and subscribers are connected to each other through a network. The network is a "store and forward" network whose routing is "content-based." The basic quanta of information is called an "event." Publishers publish events and subscribers subscribe to events that match criteria defined by the subscriber. Publication and subscription are performed asynchronously. Publishers and subscribers do not have direct knowledge of each other. The system receives a published event from a publisher and routes the event to all appropriate subscribers. Each subscriber is guaranteed to receive all events published on the system if, and only if, they match the subscription criteria specified by the subscriber.

Abstract: A method and apparatus for publishing and receiving events to a network. A plurality of "publisher" entities publish information and a plurality of "subscriber" entities request and use the information. Publishers and subscribers are connected to each other through a network. The network is a "store and forward" network whose routing is "content-based." The basic quanta of information is called an "event." Publishers publish events and subscribers subscribe to events that match criteria defined by the subscriber. Publication and subscription are performed asynchronously. Publishers and subscribers do not have direct knowledge of each other. The system receives a published event from a publisher and routes the event to all appropriate subscribers. Each subscriber is guaranteed to receive all events published on the system if, and only if, they match the subscription criteria specified by the subscriber.