JabPreface - Revision history

Uncopy: content navi added

Uncopy — Fri, 18 Sep 2009 14:23:48 GMT

content navi added

←Older revision		Revision as of 14:23, 18 September 2009
Line 1:		Line 1:
		+	{{Content Programming Jabber}}
	<br>		<br>
	=Programming Jabber=		=Programming Jabber=

Mikeh at 04:37, 17 September 2006

Mikeh — Sun, 17 Sep 2006 04:37:59 GMT

←Older revision		Revision as of 04:37, 17 September 2006
Line 2:		Line 2:
	=Programming Jabber=		=Programming Jabber=
	<br>		<br>
		+	For Wiki terms and conditions, please see:
		+	* [[Terms of Service]]
		+	* [[Editing Policy]]
		+	* [[Uploading/contribution Policy]]
		+	* [[Discussion (Traditional Legal Frameworks, Open Project Frameworks, Differences)]]
		+	<br>
		+
	<big>Original Book was Copyright 2002 O'Reilly Media, Inc. All rights reserved.</big>		<big>Original Book was Copyright 2002 O'Reilly Media, Inc. All rights reserved.</big>

Mikeh: /* The History of Jabber */

Mikeh — Sun, 17 Sep 2006 04:32:31 GMT

The History of Jabber

←Older revision		Revision as of 04:32, 17 September 2006
Line 54:		Line 54:
	==The History of Jabber==		==The History of Jabber==
	<br> Jeremie Miller started the Jabber project early in 1998, and it was announced to the public in January 1999. To understand why Jabber came about, and in the form it took, let's look briefly at what existed in the IM world before Jabber.		<br> Jeremie Miller started the Jabber project early in 1998, and it was announced to the public in January 1999. To understand why Jabber came about, and in the form it took, let's look briefly at what existed in the IM world before Jabber.
-
	<br>		<br>
-
	===The Pre-Jabber History===		===The Pre-Jabber History===
	<br> While the concept of live chat systems has existed for many years, with commands such as Unix's talk and VMS's phone, IM as we know it today existed as a concept and a handful of systems from companies such as Mirabilis, AOL, Microsoft, and Yahoo!. These systems (ICQ from Mirabilis, AIM from AOL, MSN from Microsoft, and Yahoo!IM from Yahoo!) allowed their users to chat to one another and avail themselves of IM-related services. However, an AIM user couldn't chat with an ICQ user, and MSN users couldn't interact with Yahoo!IM users. Each system was effectively closed to the outside world.		<br> While the concept of live chat systems has existed for many years, with commands such as Unix's talk and VMS's phone, IM as we know it today existed as a concept and a handful of systems from companies such as Mirabilis, AOL, Microsoft, and Yahoo!. These systems (ICQ from Mirabilis, AIM from AOL, MSN from Microsoft, and Yahoo!IM from Yahoo!) allowed their users to chat to one another and avail themselves of IM-related services. However, an AIM user couldn't chat with an ICQ user, and MSN users couldn't interact with Yahoo!IM users. Each system was effectively closed to the outside world.

Mikeh: /* Preface */

Mikeh — Sun, 17 Sep 2006 04:31:52 GMT

Preface

←Older revision		Revision as of 04:31, 17 September 2006
Line 23:		Line 23:
	* Jabber is an ''implementation'' of the set of protocols.<br>		* Jabber is an ''implementation'' of the set of protocols.<br>
	* Jabber is an idea whose time has come. <br>		* Jabber is an idea whose time has come. <br>
-	~~<br>~~In fact, all these answers are right. Jabber is a set of protocols expressed within XML that allow people and applications to converse with one another. Sure, TCP sockets, STDIN/STDOUT, infrared, voice input, and teletype mechanisms all allow people and applications to converse; the difference is that Jabber provides a structured, extensible framework for exchanging all kinds of information.	+	In fact, all these answers are right. Jabber is a set of protocols expressed within XML that allow people and applications to converse with one another. Sure, TCP sockets, STDIN/STDOUT, infrared, voice input, and teletype mechanisms all allow people and applications to converse; the difference is that Jabber provides a structured, extensible framework for exchanging all kinds of information.
	<br>This is all rather abstract, so what do we mean by "extensible framework for exchanging information"? Taking it one word at a time: <br>		<br>This is all rather abstract, so what do we mean by "extensible framework for exchanging information"? Taking it one word at a time: <br>

Mikeh: /* Preface */

Mikeh — Sun, 17 Sep 2006 04:31:27 GMT

Preface

←Older revision		Revision as of 04:31, 17 September 2006
Line 23:		Line 23:
	* Jabber is an ''implementation'' of the set of protocols.<br>		* Jabber is an ''implementation'' of the set of protocols.<br>
	* Jabber is an idea whose time has come. <br>		* Jabber is an idea whose time has come. <br>
-	<br> In fact, all these answers are right. Jabber is a set of protocols expressed within XML that allow people and applications to converse with one another. Sure, TCP sockets, STDIN/STDOUT, infrared, voice input, and teletype mechanisms all allow people and applications to converse; the difference is that Jabber provides a structured, extensible framework for exchanging all kinds of information. <br> This is all rather abstract, so what do we mean by "extensible framework for exchanging information"? Taking it one word at a time: <br>	+	<br>In fact, all these answers are right. Jabber is a set of protocols expressed within XML that allow people and applications to converse with one another. Sure, TCP sockets, STDIN/STDOUT, infrared, voice input, and teletype mechanisms all allow people and applications to converse; the difference is that Jabber provides a structured, extensible framework for exchanging all kinds of information.
		+	<br>This is all rather abstract, so what do we mean by "extensible framework for exchanging information"? Taking it one word at a time: <br>

	; Extensible		; Extensible

Mikeh: /* How to Contact Us */

Mikeh — Sun, 17 Sep 2006 04:26:15 GMT

How to Contact Us

←Older revision		Revision as of 04:26, 17 September 2006
Line 340:		Line 340:
	<br> We have tested and verified the information in this book to the best of our ability, but you may find that features have changed (or even that we have made mistakes!). Please let us know about any errors you find, as well as your suggestions for future editions, by writing:		<br> We have tested and verified the information in this book to the best of our ability, but you may find that features have changed (or even that we have made mistakes!). Please let us know about any errors you find, as well as your suggestions for future editions, by writing:

-	: O'Reilly ~~& Associates~~, Inc. 1005 Gravenstein Highway North : Sebastopol, CA 95472 (800) 998-9938 (in the U.S. or Canada) (707) : 829-0515 (international/local) (707) 829-0104 (fax) You can also send us messages electronically. To be put on the mailing list or to request a catalog, send email to:	+	: O'Reilly Media, Inc. 1005 Gravenstein Highway North : Sebastopol, CA 95472 (800) 998-9938 (in the U.S. or Canada) (707) : 829-0515 (international/local) (707) 829-0104 (fax) You can also send us messages electronically. To be put on the mailing list or to request a catalog, send email to:

	: [mailto:info@oreilly.com] To ask technical questions or comment on the book, send email to:		: [mailto:info@oreilly.com] To ask technical questions or comment on the book, send email to:

Mikeh: /* IM System Features */

Mikeh — Sun, 17 Sep 2006 04:22:45 GMT

IM System Features

←Older revision		Revision as of 04:22, 17 September 2006
Line 148:		Line 148:
	: implement the Jabber protocol, such as <tt>Net::Jabber</tt>,		: implement the Jabber protocol, such as <tt>Net::Jabber</tt>,
	: <tt>Jabber::Connection</tt>, <tt>Jabberpy</tt>, and		: <tt>Jabber::Connection</tt>, <tt>Jabberpy</tt>, and
-	: <tt>JabberBeans</tt>, are available for many languages (here, for : Perl, Python, and Java).	+	: <tt>JabberBeans</tt>, are available for many languages (here, for
		+	: Perl, Python, and Java).
	: With Jabber, it is especially relevant to		: With Jabber, it is especially relevant to
	: stress that the "weight balance" in complexity terms, between the		: stress that the "weight balance" in complexity terms, between the

Mikeh: /* Preface */

Mikeh — Sun, 17 Sep 2006 04:14:50 GMT

Preface

←Older revision		Revision as of 04:14, 17 September 2006
Line 36:		Line 36:
	; Exchanging		; Exchanging
	: Conversation is two-way, and it takes many forms		: Conversation is two-way, and it takes many forms
-	: question and answer,	+	: question and answer, notification, compartmentalized discussion,
-	: notification, compartmentalized discussion, and simple chat. Jabber	+	: and simple chat. Jabber supports all these different types of conversation and more.
-	: supports all these different types of conversation and more.	+
	; Information		; Information
	: One doesn't really say that ''information'' is exchanged in a		: One doesn't really say that ''information'' is exchanged in a

Mikeh: /* Preface */

Mikeh — Sun, 17 Sep 2006 04:07:09 GMT

Preface

←Older revision		Revision as of 04:07, 17 September 2006
Line 17:		Line 17:
	<br>		<br>
	=Preface=		=Preface=
-	<br> What is Jabber? Depending on who you ask, the answer to that question could be any one (or all) of the following: <br> * Jabber is a technology.	+	<br> What is Jabber? Depending on who you ask, the answer to that question could be any one (or all) of the following: <br>
-	<br>	+	* Jabber is a technology. <br>
	* Jabber is a protocol (or set of protocols).<br>		* Jabber is a protocol (or set of protocols).<br>
	* Jabber is an XML-based Instant Messaging (IM) system.<br>		* Jabber is an XML-based Instant Messaging (IM) system.<br>

Mikeh: /* Preface */

Mikeh — Sun, 17 Sep 2006 04:06:31 GMT

Preface

←Older revision		Revision as of 04:06, 17 September 2006
Line 22:		Line 22:
	* Jabber is an XML-based Instant Messaging (IM) system.<br>		* Jabber is an XML-based Instant Messaging (IM) system.<br>
	* Jabber is an ''implementation'' of the set of protocols.<br>		* Jabber is an ''implementation'' of the set of protocols.<br>
-	* Jabber is an idea whose time has come.	+	* Jabber is an idea whose time has come. <br>
	<br> In fact, all these answers are right. Jabber is a set of protocols expressed within XML that allow people and applications to converse with one another. Sure, TCP sockets, STDIN/STDOUT, infrared, voice input, and teletype mechanisms all allow people and applications to converse; the difference is that Jabber provides a structured, extensible framework for exchanging all kinds of information. <br> This is all rather abstract, so what do we mean by "extensible framework for exchanging information"? Taking it one word at a time: <br>		<br> In fact, all these answers are right. Jabber is a set of protocols expressed within XML that allow people and applications to converse with one another. Sure, TCP sockets, STDIN/STDOUT, infrared, voice input, and teletype mechanisms all allow people and applications to converse; the difference is that Jabber provides a structured, extensible framework for exchanging all kinds of information. <br> This is all rather abstract, so what do we mean by "extensible framework for exchanging information"? Taking it one word at a time: <br>