Abstract: In order to optimize efficiency of deserialization, a serialization cache is maintained at an object server. The serialization cache is maintained in conjunction with an object cache and stores serialized forms of objects cached within the object cache. When an inbound request is received, a serialized object received in the request is compared to the serialization cache. If the serialized byte stream is present in the serialization cache, then the equivalent object is retrieved from the object cache, thereby avoiding deserialization of the received serialized object. If the serialized byte stream is not present in the serialization cache, then the serialized byte stream is deserialized, the deserialized object is cached in the object cache, and the serialized object is cached in the serialization cache.

Abstract: In order to optimize efficiency of serialization, a serialization cache is maintained at an object server. The serialization cache is maintained in conjunction with an object cache and stores serialized forms of objects cached within the object cache. When an object is to be sent from the server to the client, a serialization module determines if a serialized form of the object is stored in the serialization cache. If the object is already serialized within the serialization cache, the serialized form is retrieved and provided to the client. Otherwise, the object is serialized, the object is cached in the object cache and the serialized form of the object is cached in the serialization cache.

Abstract: In a distributed object computing system, a server application may create multiple, uniquely identified, server contexts that each provide one or more services to a service consumer (client). Instead of creating a connection to a client for each server context, a single connection can be used. A service request handler may be configured to handle service requests for each server context. Service requests may be generated in the client with a service context identity. When a service request is received by the server application, the service request handler resolves the service context identity and forwards the service request to the appropriate server context.

Abstract: Content such as advertisements received into a mobile device may be more appropriately displayed on an alternative device remote from the mobile device. When ad content is received into the mobile device, the user may perform a physical gesture such as movement of the device or an associated motion sensor. The physical gesture is analyzed in the mobile device and causes the ad content to be redirected to the remote device. Additional physical gestures by the user can be interpreted in the mobile device to manipulate the content on the remote device.

Abstract: During communication of a large data message from a client application to a server application, requirements to communicate smaller control messages can arise. To facilitate timely communication of control messages, a client application may include a chunking module that divides a data message into chunks that can be sent as a sequence of individual data message packets. When a control message needs to be sent, the sequence of data message packets can be interrupted to send a control message packet. At the server application, the sequence of message packets is processed so that data message packets are appended to a data message and control messages are extracted for immediate processing.

Abstract: In order to determine the location of wireless network devices without inherent location capabilities, a wireless network device such as an access point can receive geolocation information from transient data sources such as mobile devices requiring network access from the access point. The access point stores geolocation records including location coordinates received from the transient data sources. The geolocation records can be processed to determine the position and movement of the access point. The geolocation records and/or location information can be passed to other transient clients that do not have inherent location capability.

Abstract: When service requirements require moving of services registered with an object request broker (ORB) at a source server, continuity of service to service requests from clients may be provided by queuing the service requests at the source server. A server context with the same GUID as a source server context may be established at a destination server. URLs for the moved services may be registered with a destination ORB which may then begin receiving service requests. The source server may then respond to the queued service requests with respective URLs for the services registered at the destination ORB. Endpoints at the clients may be updated with the new URLs prior to resending the service requests. The movement of the ORB to the destination server may thus be transparent to the client application.

Abstract: To estimate the number of casualties at an event, a query may be sent to mobile device history database(s) associated with one or more mobile base stations that provide service coverage to an area that encompasses the event. The query determines the number of abnormal disconnects from the base station in a time interval immediately after the event. From the query response, a calculation may be performed of the number of casualties, with some or all of these abnormal disconnects being considered to indicate a casualty. Additional parameters can be applied to a casualty calculation, such as the percentage of persons in an area who would normally carry a mobile device that is connected to the one or more base stations.

Abstract: Mobile agents can be deployed to mobile devices within specific regions of interest to achieve specific goals in respect of events occurring in the region of interest. In order to ensure that the agent can persist within the region of interest until the agent goals are achieved, the agent is configured to locate other devices within the region of interest and to propagate itself, by moving or copying itself, to those other devices. The region of interest may be a mobile and/or dynamic region of interest defined by, for example, a proximity to one or more mobile wireless access points or by an overlapping peer-to-peer communication range of a plurality of mobile devices that are configured to support the agent.

Abstract: In a mobile device, one of a plurality of network transports may be used for a connection request. The ideal network transport may be selected by executing a connection selection policy that is stored within the device. The connection selection policy may include one or more network transport evaluators that are each configured to weight the available network transports according to various criteria. Examples of network transport evaluators include evaluators that are dependent on geolocation, security levels, or battery status.

Abstract: In distributed object computing, messages from a source node to a destination node are often required to be routed via one or more intermediate nodes. In order to enhance efficiency of the relay process, a message envelope of a message may include a node list field that specifies the routing path of the message. The communication protocol for communicating the message may specify that when a message is received into a particular node, the node analyzes the node list field. If the identity of the node is last in the node list field, then the node is the destination node and thus the node unmarshals the message. Otherwise, the node forwards the message to the next node in the field list without unmarshalling the message.

Abstract: In order to provide filtering of content to be presented on a mobile device, a gesture-based preferencing system and method may be employed. When content is presented to a user, the user may indicate a positive or negative preference toward that content by making a gesture. The gesture may be detected by a motion sensor and the preference of the content indicated by the gesture may be stored in a preference datastore. The preference may be used to subsequently filter content that is to be presented to the user.

Abstract: In order to enable a dynamic handshake procedure, a device may be configured with a list of handshake contributors. Contributors with connection handshake properties may be added to the contributor list. To perform handshake, the contributor list is processed to extract the connection handshake properties of each contributor to the handshake. Handlers for handling the connection handshake properties may also be dynamically added and invoked when a handshake is received.

Abstract: In order to manage stale data on a network of computer systems, a file harvester agent may be configured with a list of stale data files to be deleted. The file harvester agent may be deployed to the computer systems of a network. When executed in a computer system, the file harvester agent searches the file system of the computer system to locate any files or data indicated in the file list. Any located data files are deleted. Once the agent has finished processing the file list on a computer system, the agent can copy or replicate itself to other computer systems of the network in accordance with a pre-configured itinerary.

Abstract: To provide proxy address neutrality, in particular for mobile server devices, a server application can register its network address with a discovery application. Whenever the server application acquires a new network address, the server application updates the discovery application. A client application providing proxy services for the server application can invoke calls to the server client using the network address for the server application that is currently stored in the client device. If the current network address is invalid, the client application obtains an updated network address from the discovery application.

Abstract: In order to enable a dynamic handshake procedure, a client device is configured with a list of handshake contributors. The client device initiates a handshake by determining the handshake contributors and writing properties of the handshake contributors in a client handshake, which is then sent to a server device. The client handshake is processed at the server device by invoking an appropriate handler, which handles the handshake result. The server can also send its contributors and their properties to the client. Once the client receives the properties, the client can call an appropriate handler to handle the properties. Connections may be created based on the exchanged properties. New contributors and contributor handlers may be added to both the client and server devices.

Abstract: In order to optimize efficiency of deserialization, a serialization cache is maintained at an object server. The serialization cache is maintained in conjunction with an object cache and stores serialized forms of objects cached within the object cache. When an inbound request is received, a serialized object received in the request is compared to the serialization cache. If the serialized byte stream is present in the serialization cache, then the equivalent object is retrieved from the object cache, thereby avoiding deserialization of the received serialized object. If the serialized byte stream is not present in the serialization cache, then the serialized byte stream is deserialized, the deserialized object is cached in the object cache, and the serialized object is cached in the serialization cache.

Abstract: An interface generator (250) for remote enabling class files (252) without an associated interface is provided that includes a class reader (256), a reflection module (258), and an interface generation module (262). The class reader (256) receives a class file (252) from an input list. The reflection module (258) determines a name of the class file, public methods of the class file, and a signature of each of the public methods of the class file. The interface generation module (262) generates an interface (254) for the class file (252) using the name of the class file, the public methods of the class file, and the signature for each of the public methods of the class file determined by the reflection module (258).

Abstract: A client object on a first network requests access to a server object on a second network. A third network connects the first network to the second network. A connections properties table is associated with the first network and includes an entry for each of one or more second networks that are accessible by the first network. The connections properties table also includes connection protocol information for accessing the one or more second networks. A connection manager generates a boundary traversal key for requests for access to server objects that have a corresponding entry in the connections properties table. The boundary traversal key is generated from the corresponding connection protocol information in the connections properties table.

Abstract: A system for server-side communication support in a distributed computing environment is provided that includes a local reference (202) to a server object (110) on a server system (104). The local reference (202) provides a location of the server object (110) and a type of the server object (110). The local reference (202) resides within a server-side object request broker (114). A type object (204) is accessible by the local reference (202) using the type of the server object (110) from the local reference (202). The type object (204) represents a class of the server object (110). One or more specialized function objects (206) are linked to the type object (204) and correspond in number to one or more methods (190) of the server object (110). The one or more specialized function objects (206) provide wrapper functionality for each method (190) of the server object (110). Each specialized function object (206) provides access to a corresponding one of the one or more methods (190) of the server object (110).