
	Where results make sense

Topic: Extensible Messaging and Presence Protocol

Related Topics

XAML

RSS (protocol)

XUL

XBL

List of markup languages

CHTML

SyncML

In the News (Thu 10 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	RFC 3921 (rfc3921) - Extensible Messaging and Presence Protocol (XMPP): In
		Presence Syntax Presence stanzas are used qualified by the 'jabber:client' or 'jabber:server' namespace to express an entity's current network availability (offline or online, along with various sub-states of the latter and optional user-defined descriptive text), and to notify other entities of that availability.
		Session Establishment Most instant messaging and presence applications based on XMPP are implemented via a client-server architecture that requires a client to establish a session on a server in order to engage in the expected instant messaging and presence activities.
		Broadcast initial presence from the full JID (e.g., ) of the user to all contacts that are subscribed to the user's presence information; such contacts are those for which a JID is present in the user's roster with the 'subscription' attribute set to a value of "from" or "both".
	www.faqs.org /rfcs/rfc3921.html (8941 words)

	Extensible Messaging and Presence Protocol
		Extensible Messaging and Presence Protocol, or XMPP, is an open, XML-based protocol for near real-time extensible messaging and presence[?].
		It is the core protocol of the Jabber Instant Messaging and Presence technology which is currently deployed on thousands of servers across the Internet and is used by millions of people worldwide.
		The IETF XMPP working group aims to adapt the XMPP for use as an IETF Instant Messaging and Presence technology.
	www.ebroadcast.com.au /lookup/encyclopedia/xm/XMPP.html (71 words)

	RFC 3920 (rfc3920) - Extensible Messaging and Presence Protocol (XMPP): Co
		While XMPP provides a generalized, extensible framework for exchanging XML data, it is used mainly for the purpose of building instant messaging and presence applications that meet the requirements of RFC 2779.
		Message Semantics The stanza kind can be seen as a "push" mechanism whereby one entity pushes information to another entity, similar to the communications that occur in a system such as email.
		For compliance purposes, we draw a distinction between core protocols (which MUST be supported by any server or client, regardless of the specific application) and instant messaging protocols (which MUST be supported only by instant messaging and presence applications built on top of the core protocols).
	www.faqs.org /rfcs/rfc3920.html (13705 words)

	RFC 3921 - Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence
		No reply to the message is expected, and a compliant client SHOULD present the message in an Saint-Andre Standards Track [Page 4] RFC 3921 XMPP IM October 2004 interface that appropriately differentiates the message from standalone messages, chat sessions, or groupchat sessions (e.g., by not providing the recipient with the ability to reply).
		If the presence stanza possesses no 'type' attribute, it MAY contain any of Saint-Andre Standards Track [Page 7] RFC 3921 XMPP IM October 2004 the following child elements (note that the child MAY be sent in a presence stanza of type "unavailable" or, for historical reasons, "subscribe"): 1.
		If the message is being sent Saint-Andre Standards Track [Page 13] RFC 3921 XMPP IM October 2004 outside the context of any existing chat session or received message, the value of the 'to' address SHOULD be of the form rather than of the form .
	www.packetizer.com /rfc/rfc3921 (8952 words)

	Extensible Messaging and Presence Protocol - Wikipedia, the free encyclopedia
		It is the core protocol of the Jabber Instant Messaging and Presence technology which is currently deployed on thousands of Jabber servers across the Internet and is used by millions of people worldwide.
		RFC 3920, Extensible Messaging and Presence Protocol (XMPP): Core which describes client-server messaging using two open ended XML streams.
		XML streams consist of , and (info/query) as illustrated in the example client-server conversation.
	en.wikipedia.org /wiki/Extensible_Messaging_and_Presence_Protocol (526 words)

	RFC3923 - End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP). : ...
		Case #2: The receiving application understands the protocol and is able to decrypt the payload and verify the sender's signature.
		Detailed security considerations for instant messaging and presence protocols are given in [IMP-REQS] (Sections 5.1 through 5.4), and for XMPP in particular are given in [XMPP-CORE] (Sections 12.1 through 12.6).
		Such a gateway MUST be compliant with the minimum security requirements of the instant messaging and presence protocols with which it interfaces.
	www.opensourcemanuals.org /rfc/3923 (3979 words)

	Cover Pages: Jabber XML Protocol
		These documents, which formalize the XML streaming protocols first developed by the Jabber open-source community in 1999, are the result of two years of work by the IETF's Extensible Messaging and Presence Working Group and represent the state of the art in open instant messaging (IM) and presence technologies.
		XMPP is the core protocol used in the popular Jabber open source and Jabber, Inc. commercial instant messaging systems and is the result of the collaborative efforts of a worldwide group of software architects, developers and companies that comprise the Jabber community.
		Presence is useful to learn things like 'Jon is online, but is busy.' But it could be modified with filters to say 'But I'm available to chat with anyone on the O'Reilly e-mail book team.' This should even be doable with current Jabber filters and presence.
	www.oasis-open.org /cover/jabber.html (9285 words)

	Cover Pages: Extensible Messaging and Presence Protocol (XMPP)
		While XMPP provides a generalized, extensible framework for exchanging XML data, it is used mainly for the purpose of building instant messaging and presence applications that meet the requirements of RFC 2779." The XMPP Core specification "includes guidelines to ensure that extensions are possible without conflicts or breaking core interoperability.
		The eXtensible Messaging and Presence Protocol (XMPP) is an open XML protocol for near-real-time messaging and presence.
		The protocol was developed originally within the Jabber community starting in 1998, and since 2001 has continued to evolve under the auspices of the Jabber Software Foundation and now the XMPP WG.
	xml.coverpages.org /xmpp.html (6762 words)

	RFC 3921 - Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence. P. Saint-Andre, Ed..
		RFC 3921 XMPP IM October 2004 outside the context of any existing chat session or received message, the value of the 'to' address SHOULD be of the form rather than of the form .
		RFC 3921 XMPP IM October 2004 has not blocked outbound presence notifications, and (3) from whom the server has not received a presence error during the user's session (as well as to any of the user's other available resources).
		RFC 3921 XMPP IM October 2004 Example 13: User's server broadcasts unavailable presence information to contact as well as to the person to whom the user sent directed presence: type='unavailable' from='romeo@example.net/orchard' to='juliet@example.com' xml:lang='en'> gone home from='romeo@example.net/orchard' to='nurse@example.com' xml:lang='en'> gone home 6.
	rfc.sunsite.dk /rfc/rfc3921.html (8728 words)

	Extensible Messaging and Presence Protocol (xmpp) Charter
		XMPP is an open, XML-based protocol for near real-time extensible messaging and presence.
		A major goal of the working group will be to extend the current XMPP protocols to provide finished support for RFC 2779-compliant security mechanisms, including authentication, privacy, access control and end-to-end as well as hop-by-hop message security.
		In addition, instant messaging includes the notion of presence information so authorized users can determine if their correspondents are available.
	www3.ietf.org /proceedings/03mar/108.htm (924 words)

	RFC 3920 - Extensible Messaging and Presence Protocol (XMPP): Core
		C: from='juliet@example.com' to='romeo@example.net' xml:lang='en'> C: Art thou not Romeo, and a Montague? C: S: from='romeo@example.net' to='juliet@example.com' xml:lang='en'> S: Neither, fair saint, if either thee dislike. S: C: S: Saint-Andre, Ed.
		Standards Track [Page 54] RFC 3920 XMPP Core October 2004 SHOULD NOT be used as the error message presented to a user, but MAY be shown in addition to the error message associated with the included condition element (or elements).
		Standards Track [Page 62] RFC 3920 XMPP Core October 2004 (which MUST be supported by any server or client, regardless of the specific application) and instant messaging protocols (which MUST be supported only by instant messaging and presence applications built on top of the core protocols).
	www.packetizer.com /rfc/rfc3920 (13254 words)

	XMPP: Extensible Messaging and Presence Protocol Overview
		Extensible Messaging and Presence Protocol (XMPP) is designed to stream XML elements for near-real-time messaging, presence, and request-response services.
		XMPP is based on the Jabber protocol, an open and popular protocol for instant messaging.
		A gateway is a special-purpose server-side service whose primary function is to translate XMPP into the protocol used by a foreign (non-XMPP) messaging system, as well as to translate the return data back into XMPP.
	www.javvin.com /protocolXMPP.html (461 words)

	XMPP, eXtensible Messaging and Presence Protocol (Site not responding. Last check: 2007-11-04)
		XMPP is a simplified and specialized protocol for streaming XML elements in order to exchange structured information in close to real time.
		XMPP has been adapted from the protocols originally developed in the Jabber open-source community, which can be thought of as "XMPP 0.9".
		[RFC 3920] Extensible Messaging and Presence Protocol (XMPP): Core.
	www.networksorcery.com /enp/protocol/xmpp.htm (125 words)

	XMPP Gets Second Vote of Confidence
		Supporters of the Extensible Messaging and Presence Protocol -- also known as the Jabber protocol -- received another validation of their work, as the steering body of the Internet Engineering Task Force approved the second of the movement's major specifications to become an Internet standard.
		It also could mean that the protocol will see greater adoption by developers looking to bake an IM protocol into their applications.
		defines some extensions to the core streaming protocols in order to do some of the functionality that's expected of a basic instant messaging and presence system -- like contact lists, being able to block other users from taking to you, detailed information on how the subscriptions work for presence...
	www.instantmessagingplanet.com /enterprise/article.php/3311211 (853 words)

	XMPP - EnterpriseNetworkingPlanet - News, trends and advice for network managers
		Short for Extensible Messaging and Presence Protocol, an open, XML-based protocol for server-to-server near-real-time extensible instant messaging and presence.
		XMPP also is known as the Jabber protocol because Jabber is based on XMPP.
		Jabber is not, however, the only instant messaging application that relies on XMPP.
	networking.webopedia.com /TERM/X/XMPP.html (90 words)

	XMPP (Extensible Messaging and Presence Protocol)
		XMPP is an XML streaming protocol for presence and messaging routing.
		When nodes connect to a server, they authenticate using credentials from the local directory system, specify a resource and tell to the server to announce their presence to subscribers (for example, the buddies on one user's roster).
		Servers find, connect and authenticate to one another, letting any node connected to the community talk to any other node regardless of their home server (domain), as long as no privacy or business rules are violated.
	www.networkworld.com /details/6836.html?def (839 words)

	[No title]
		The most common use of this structure is to identify an instant messaging user, the server to which the user connects, and the user's connected resource (e.g., a specific client) in the form of
		The initiating entity chooses one method from the list and sends it to the receiving entity as the value of the 'mechanism' attribute possessed by an element, optionally including an initial response to avoid a round trip.
		The stanza-kind is one of message, presence, or iq.
	www.ietf.org /rfc/rfc3920.txt (15130 words)

Try your search on: Qwika (all wikis)