Talk:Extensible Messaging and Presence Protocol

From Wikipedia, the free encyclopedia

I'm going to delete the reference to Opetec's Shisha product. It's not open source as stated and the link provided is "404 Not found," anyway. Searching independently produced a link at the Opetec web site saying that the product is still unreleased, scheduled for release in 3Q 2005, and states that even the basic functionality of the product is secret:

Developer Opetec, Publisher: TBA Due for release: Q3 2005
Platform(s): Linux, Windows, MacOS, Solaris, Symbian OS Description:
Unfortunatly we are unwilling to reveal the true features at this stage, but we will say, without any marketing speak that it is the next revolution in communication and interoperability. For the developers we will be releasing a fully open toolkit to allow developers to use the features of Shisha on any existing platform. If you are interested in investing in Shisha or developing the project further, then feel free to contact Opetec - we will communicate more information with investors who appear to be serious and who are interested in investing in the technology sector.

There's not even a basis for saying that Shisha, whatever it is, has anything to do with XMPP.
Zigamorph 15:32, 12 October 2005 (UTC)

Contents

[edit] Changes to example section

I changed the example section a little bit in an attempt to make it easier to follow. The previous names (kuusipuu and tero) and the test server (amessage.de) were very different and made the confusing example a little more confusing. I picked more common and generic-sounding names, alice, bob, and example.org. --Foofy 18:34, 17 January 2006 (UTC)

The example section has now been deleted, with the reason that it was 'not very useful'. Personally, I was quite curious as to the format of the XML streams, so I ended up going and looking at the example in the article history. Thus, it was useful to me. However, I'm not sure whether said chunk of XML belongs in the article or not, in that I don't know whether anyone else would find it useful - opinions? 86.10.97.74 23:54, 29 April 2007 (UTC)

[edit] Implementations section

Isn't it better to replace that section with the category XMPP? NaturalBornKiller 18:15, 18 May 2006 (UTC)

The section that should be removed IMO is now called "Uptake and clients".--NaturalBornKiller 10:22, 28 May 2007 (UTC)
Well, a section documenting larger projects which adopted the protocol would be very warranted, although it should be more prose and less of a list. I certainly agree that we don't need another list of Jabber clients. We already have list of Jabber client software which is in serious need of improvement. -- intgr #%@! 11:45, 28 May 2007 (UTC)

[edit] XMPP or Jabber?

It seem to me that XMPP and Jabber are exactly the same thing, but Jabber seems to be a more common name. So shouldn't the article be talking about Jabber instead of XMPP which is a technical name? Wikipedia:Naming convention would seem to indicate that the name Jabber should be used. Or can someone come up with a reason why XMPP should be used instead? Pafcu 09:15, 26 July 2007 (UTC)

Jabber ist just an imlementation of the XMPP. Comparable to the relation between IRC and its protocol.

maybe more between MIRC or XCHAT, and the IRC protocol?134.225.217.52 (talk) —Preceding comment was added at 22:23, 27 April 2008 (UTC)

[edit] projects that use xmpp

i don't know if it's important, but i think that google's android is using this to send "intents" between devices and the olpc uses this as well (i just passed by, please delete my comment if it's not important enough to be included in the article) --84.108.246.171 07:18, 14 November 2007 (UTC)

[edit] Port (5222)

Why standart XMPP port (5222/tcp) wasn't mentioned in the arcticle? _Vi (talk) 12:03, 6 April 2008 (UTC)