Abstract: Collaboration between collaborative endpoints may be facilitated by a serverless publication service of a collaborative services platform. The serverless publication service may be configured to accept communicative connections from the collaborative endpoints. Users of the collaborative services platform may publish their associated collaborative presences with the serverless publication service. For example, the collaborative presence of a user may include information with respect to valid collaborative endpoints for the user and collaborative capabilities at those endpoints. Subscriptions to published collaborative presences may be placed through the serverless publication service. A collaborative presence subscribe message may specify a subscription to a collaborative presence of a user. Upon receipt of a presence subscribe message, if there is no subscription policy with respect to the sender, the recipient may be queried for a subscription policy with respect to the sender.

Abstract: A method of converting a peer name to a PNRP DNS is disclosed. The method may take a peer name and encode it into a common DNS name. The method may also take a PNRP DNS name and convert it to a peer name.

Abstract: An extensible data structure for messages in a peer to peer name resolution protocol is presented. This message data structure utilizes a number of fields, each containing a message element. Preferably, the first field is the message header that includes protocol information and identifies the type of message. Each message element contains a number of fields. These message element fields include a type field, a length field, and the content or payload of the message element. In one embodiment, at least ten messages are formed for proper operation of a Peer To Peer Name Resolution Protocol (PNRP), including RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR messages.

Abstract: The managed system and methods of the present invention are segmented into 3 main areas: Clouds, Registrations, and Resolvers. The cloud object provides information about the clouds that are available. If a could is available, the Registration object can be used to register endpoints with the P2P name resolution protocol. Finally, if an application developer wishes to resolve a peer name to an IP address, they simply use the resolver object. The clouds may be monitored for state changes in one embodiment of the present invention through a CloudWatcher object.

Abstract: A method of converting a peer name to a PNRP DNS is disclosed. The method may take a peer name and encode it into a common DNS name. The method may also take a PNRP DNS name and convert it to a peer name.

Abstract: Systems and methods are described for facilitiating collaboration and/or communication in a peer-to-peer serverless system. The system may transmit to other computing systems associated with other entities information regarding presence information associated with a user entity. Also, the system may request of other computing systems associated with other entities information regarding presence information associated with the other entities. Presence information may generally indicate the willingness and/or ability of an entity to communicate and/or collaborate with other entities, for example.

Abstract: Collaboration between collaborative endpoints may be facilitated by a serverless publication service of a collaborative services platform. The serverless publication service may be configured to accept communicative connections from the collaborative endpoints. Users of the collaborative services platform may publish their associated collaborative presences with the serverless publication service. For example, the collaborative presence of a user may include information with respect to valid collaborative endpoints for the user and collaborative capabilities at those endpoints. Subscriptions to published collaborative presences may be placed through the serverless publication service. A collaborative presence subscribe message may specify a subscription to a collaborative presence of a user. Upon receipt of a presence subscribe message, if there is no subscription policy with respect to the sender, the recipient may be queried for a subscription policy with respect to the sender.

Abstract: A system, method, and computer product for a host node to participate in a peer network through a proxy, wherein the peer network includes a plurality of nodes, each node having a peer identifier (ID) and a cache of peer IDs for one or more known nodes, is provided. The method comprises acquiring the peer ID of a proxy node in the peer network; requesting the proxy node to act as a proxy; sending a message to at least one node in the peer network through the proxy node; and receiving a response from the at least one node in the peer network through the proxy node, wherein the at least one node in the peer network is unaware of a network address for the host node.

Abstract: The managed system and methods of the present invention are segmented into 3 main areas: Clouds, Registrations, and Resolvers. The cloud object provides information about the clouds that are available. If a could is available, the Registration object can be used to register endpoints with the P2P name resolution protocol. Finally, if an application developer wishes to resolve a peer name to an IP address, they simply use the resolver object. The clouds may be monitored for state changes in one embodiment of the present invention through a CloudWatcher object.

Abstract: An extensible data structure for messages in a peer to peer name resolution protocol is presented. This message data structure utilizes a number of fields, each containing a message element. Preferably, the first field is the message header that includes protocol information and identifies the type of message. Each message element contains a number of fields. These message element fields include a type field, a length field, and the content or payload of the message element. In one embodiment, at least ten messages are formed for proper operation of a Peer To Peer Name Resolution Protocol (PNRP), including RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR messages.

Abstract: A respiratory valve, especially for use in the circuits of anaesthetic gas devices, having a body member formed with two arms in a V configuration, intended for inhalation and exhalation, respectively, and a tubular mouthpiece fitting. To the two arms are connected, by joints, an inhalation fitting and an exhalation fitting, respectively; the joints retain each the fastening ring of a shutter, the resilient membrane of which closes and opens in response to the gas circulation, as required.