Abstract: A publish/subscribe interface is used to enable a non-publish/subscribe first system (such as an IP network device) to obtain status information about a publish/subscribe device that cannot be pinged by the first system. The first system sends a status request to a domain name server. The status request includes a domain name for the publish/subscribe device. Topic space maintained by a message broker in the publish/subscribe system includes status topics associated with publish/subscribe devices. The status topics contents reflect the current availability of the associated publish/subscribe device.

Abstract: A publish/subscribe interface is used to enable a non-publish/subscribe first system (such as an IP network device) to obtain status information about a publish/subscribe device that cannot be pinged by the first system. The first system sends a status request to a domain name server associated with a system known to include the publish/subscribe device. The status request includes a domain name for the publish/subscribe device. Topic space maintained by a message broker in the publish/subscribe system includes status topics associated with publish/subscribe devices. The status topics contents reflect the current availability of the associated publish/subscribe device. The domain name is mapped to a status topic associated to the publish/subscribe device identified in the status request and the contents of that status topic are retrieved. If the contents have a first value, a “good” IP address is returned to the first system. If the contents have the second value, a “bad” IP address is returned.

Abstract: A device for enabling a first computer network device to determine whether a second computer network device has an online status or an offline status includes a memory device with instructions for execution by a processor to: receive a request from the first computer network device for the status of the second computer network device; determine whether the second computer network device is online or offline; in response to a determination that the second computer network device is online, return a first network address to the first computer network device; and in response to a determination that the second computer network device is offline, return a second network address to the first computer network device, wherein the second network address is a known bad address that will not provide a response to the first computer network device.

Abstract: A publish/subscribe interface is used to enable a non-publish/subscribe first system (such as an IP network device) to obtain status information about a publish/subscribe device that cannot be pinged by the first system. The first system sends a status request to a domain name server associated with a system known to include the publish/subscribe device. The status request includes a domain name for the publish/subscribe device. Topic space maintained by a message broker in the publish/subscribe system includes status topics associated with publish/subscribe devices. The status topics contents reflect the current availability of the associated publish/subscribe device. The domain name is mapped to a status topic associated to the publish/subscribe device identified in the status request and the contents of that status topic are retrieved. If the contents have a first value, a “good” IP address is returned to the first system. If the contents have the second value, a “bad” IP address is returned.

Abstract: Message integrity in a messaging oriented middleware system is preserved by determining a message producer's level of message integrity by examination of connection details between the message producer and a messaging engine. The message producer's level of integrity is stored in a memory of the messaging engine. The message is then stored in the designated destination using the message producer's level of integrity. The message is sent from the designated destination to a consumer when it is determined that the consumer conforms to the integrity levels.

Abstract: Message integrity in a messaging oriented middleware system is preserved by determining a message producer's level of message integrity by examination of connection details between the message producer and a messaging engine. The message producer's level of integrity is stored in a memory of the messaging engine. The message is then stored in the designated destination using the message producer's level of integrity. The message is sent from the designated destination to a consumer when it is determined that the consumer conforms to the integrity levels.

Abstract: A method of assisting a user, for use in an environment comprising: a user session, an external entity session and a forms engine for generating a form. The method comprises the steps of: registering with the user session, wherein a first session is established between the user session and the forms engine; receiving a request for assistance from a user; in response to receiving the request, de-registering with the user session, wherein the first session is un-established; registering with the external entity session, wherein a second session is established between the external entity session and the forms engine; receiving input from the external entity session; and populating the form with the received input.

Abstract: A method and system for controlling message throughput rates of clients connected to a broker device in a publish/subscribe network are disclosed. The broker device determines a maximum allowable message throughput for each client connected to the broker device. If a message-producing rate of a client exceeds the maximum allowable message throughput of the client, the broker device sends a negative acknowledgement (NACK) packet to the client and messages from the client are not accepted at the broker device. The NACK packet includes a maximum allowable message throughput of the client, so the client can adjust its message-producing rate based on the maximum allowable message throughput of the client. The present invention can be applied to a publish/subscribe network as well as a TCP/IP network.

Abstract: A mechanism is provided for network communication. The mechanism establishes a connection between a network server and a network client. The connection is established using a connection-oriented protocol. The network server has a first server configuration stored in a memory of the network server. The first server configuration comprises a set of server parameters specific to a network application that the network server provides to the network client. The mechanism identifies the network client configuration. The mechanism replaces, in the memory of the network server, the first server configuration with a second server configuration. Responsive to a determination that the client configuration is incompatible with the second server configuration, the mechanism disconnects the network client.

Abstract: Methods support a sleep mode for an embedded device. Embedded devices like sensors and actuators used in wireless sensor networks have a limited power supply. To conserve energy and thus increase the lifetime of these devices, the devices should be put into a stand-by mode (also called sleep-mode) when they are not used. These methods support the sleep mode at a higher level than the MAC layer, thus avoiding the problems of prior art approaches. Methods are exemplarily described for the case of the message queuing telemetry transport protocol for sensor networks. They can easily be adapted to other protocols.

Abstract: A method and arrangement (100) for impermanent connectivity between a client unit (110) and a server (120) in a network, comprising: at the client unit, a client proxy function (114) for receiving information from/for a client application (112), for storing said information, and for relaying said information between the client unit and the server when a connectivity link (130) therebetween is established. The arrangement may further comprise a server proxy function (124), and a messaging subsystem (116, 122). The information may be SMTP, POP3, HTTP or FTP information. An FTP file ‘GET’ command may be performed by, in response to the ‘GET’ command, writing a local file at the client unit having a unique signature, and when the connectivity link is established, obtaining the requested file from the server, finding the file at the client unit having the unique signature, and over-writing the found file with the obtained file.

Abstract: There is disclosed a method, apparatus and computer program for modifying a message. A message is received from a first entity. The message contains a first level of detail appropriate to the first entity and the message is for communication to a second entity. It is determined whether the message contains a scope sensitive field. Once it has been determined that the message does contain a scope sensitive field, information is accessed indicating how to transform the scope sensitive field to a second level of detail appropriate to the second entity. The scope sensitive field is then transformed to produce the second level of detail.

Abstract: A network server for communicating with a network client over a network comprising: a client configuration detector for detecting a configuration of the network client; a server configurator for changing the configuration of the network server; a comparator for determining if the configuration of the network client is compatible with the configuration of the network server; and a server communications component for connecting with the network client using a connection-oriented protocol, wherein the server communications component is operable to disconnect the network client responsive to said comparator.

Abstract: Disclosed are a method, system and computer program product for placing a group order, mediated by a system having one or more computers, the method comprising the steps of: publishing, by a publisher, information about a quantity of a material; subscribing, via a subscriber, to a topic comprising said information; receiving, via a subscriber, said information; aggregating, via a subscriber, said information from at least one of said publishers; and responsive to said step of aggregating, selecting based on at least one criterion a best time to place said group order.

Abstract: In a system having a plurality of sources of information (102, 103, 104, 105), each source (102, 103, 104, 105) registers as being capable of providing information in respect of at least one specific class of request. When a request for information (120) is received, it is distributed to one or more sources that are registered for that class of request.

Abstract: A reduction in the amount of information written to a log used to track message activity in a messaging system is achieved by not logging message data in a log record for the put of a message if the message data has been included in a previous message and is already available in the log. On receipt of a put request a check is made to see if there is a previous occurrence of the message data in the log. If there is not a previous occurrence a log record is written which includes the message data, but if there is a previous occurrence a log record is written which does not contain the message data but a reference which can be used to locate the previous occurrence of the message data in the log. Preferably the application includes an indication on the put request that the message data has been previously used.