Abstract: A method is described to allow a device to retrieve a message, that is separated into a plurality of fragments, from a data source, wherein the method involves: establishing a first network connection with the data source; receiving a subset of the plurality of fragments; determining the first network connection has ended before completion of said message; establishing one or more subsequent network connections with the data source; and receiving any of the plurality of fragments not within the subset. The characteristics (for example: application protocol, security, speed, reach, bandwidth capability, cost of usage, network type, physical layer type, data-link layer type, or IP address of one or both of the first and second devices) of the first network connection can be potentially different than the subsequent network connections.

Abstract: A computer implemented method/system of creating and managing one or more interceptors. The method comprises the steps of intrinsically chaining the interceptors, and storing state information, in at least one of the chained interceptors, directed to a reference to the next interceptor. A server computer in a client-sever environment that includes a processor configured to generate one or more interceptors and to intrinsically chain the interceptors, and a memory associated with at least one of the chained interceptors and configured to store state information directed to a reference to the next interceptor thereof. The method/system, in various embodiments, includes dissimilar interceptors, callbacks, and flyweight pattern weighting.

Abstract: A computer implemented method/system of creating and managing one or more interceptors. The method comprises the steps of intrinsically chaining the interceptors, and storing state information, in at least one of the chained interceptors, directed to a reference to the next interceptor. A server computer in a client-sever environment that includes a processor configured to generate one or more interceptors and to intrinsically chain the interceptors, and a memory associated with at least one of the chained interceptors and configured to store state information directed to a reference to the next interceptor thereof. The method/system, in various embodiments, includes dissimilar interceptors, callbacks, and flyweight pattern weighting.

Abstract: A novel communication device (e.g., router or switch) facilitates interoperation between a plurality of middleware. The communication device has in-ports, out-ports, and a configurator. In-ports, IP0, . . . , IPm, are associated with a middleware from a plurality of middleware and out-ports, OP0, . . . , OPn, are associated with a middleware from the plurality of middleware. The configurator configures in-ports and out-ports based on a binding and transport of associated middleware and the novel communication device facilitates interoperation between middleware via a communication path between at least one configured in-port and at least one configured out-port, with the communication path allowing an incoming message to pass from said at least one configured in-port to said at least one configured out-port. Parameters ‘m’ and ‘n’ are chosen such that any of the following conditions are true: m=0 and n?1, m?1 and n=0, m=n, m=1 and n>1, m>1 and n=1, and m?n.

Abstract: A communication system is introduced to integrate middleware having in-ports, out-ports, a configurator, and intermediary elements. The configurable in-ports and out-ports are used to facilitate communication with specific middleware among a set of middleware. A configurator configures in-ports and out-ports corresponding to specific middleware, wherein each in-port and each out-port is configured based on a binding and a transport. The configured in-ports, the configured out-ports, and the intermediary elements form one or more paths over which data is moved, with each of the intermediary elements performing any of, or a combination of, the following: propagation of transaction information, transformation of data, load balancing, fault tolerance, session management, orchestration, security, or control of transaction boundaries.

Abstract: A system and method is introduced that integrates middleware components without canonicalization of data at runtime. An interface receives inputs identifying at least a first and second middleware to be made interoperative and a configurator configures at least an in-port and an out-port based on a binding and transport associated with the first and second middleware, respectively. Interoperation of the first and second middleware is effected via at least one communication path between the configured in-port and out-port, wherein the communication path allows an incoming message to pass from the in-port corresponding to said first middleware to the out-port corresponding to the second middleware without the creation of an intermediate canonical message.

Abstract: A remote mobile device periodically connects with a centralized data server to receive updated information. Because of the mobile nature of the remote device, a download of all available information may not be able to be completed during the initial network connection. When the mobile device can again reconnect to the centralized data server, the two machines are able to continue the exchange of information even if the new network connection uses different underlying technologies or different connection protocols. A fragmentation layer is used in the protocol stack above the transport layer to separate messages into chunks. By tracking which chunks are successfully sent between the two machines, the efficient exchange of messages can occur across multiple, different network connections.

Abstract: A system and method are disclosed for decreasing the number of duplicate library copies loaded into memory without endangering the security of applications in a runtime environment. In a preferred embodiment, applications in the runtime environment may be provided with a delegation classloader that identifies any libraries referenced by the delegation classloader's respective application. The delegation classloaders then delegate the task of providing the referenced libraries to a distinct software component. In a preferred embodiment, the distinct software component may be another delegation classloader or other loader adapted to look at a single library or a small set of libraries. These “atomic” classloaders can be freely shared by multiple applications since they do not expose any application's internals. Each atomic classloader preferably loads one copy of its associated library or libraries into memory.