JabChapter 1 - Revision history

Mikeh at 16:28, 7 January 2009

Mikeh — Wed, 07 Jan 2009 16:28:06 GMT

←Older revision		Revision as of 16:28, 7 January 2009
Line 1:		Line 1:
-	cbolitroclac
	{{Content Programming Jabber}}		{{Content Programming Jabber}}
	=Getting Started with Jabber=		=Getting Started with Jabber=

SitviEldro: oloraczelli

SitviEldro — Wed, 07 Jan 2009 03:12:19 GMT

oloraczelli

KruegerN at 08:58, 7 October 2006

KruegerN — Sat, 07 Oct 2006 08:58:47 GMT

←Older revision		Revision as of 08:58, 7 October 2006
Line 1:		Line 1:
-	~~<br>~~	+	{{Content Programming Jabber}}
	=Getting Started with Jabber=		=Getting Started with Jabber=
-	<br>
	==Introducing Jabber==		==Introducing Jabber==
	This book is about Jabber: the technology, protocols, ideas, and the philosophy. Jabber is about connecting things (users, applications, and so on) in an all-pervasive message plasma that flows between clients and servers, carrying content, structure, and conversations.		This book is about Jabber: the technology, protocols, ideas, and the philosophy. Jabber is about connecting things (users, applications, and so on) in an all-pervasive message plasma that flows between clients and servers, carrying content, structure, and conversations.

KruegerN: /* A Simple Script */ - fix layout

KruegerN — Wed, 27 Sep 2006 19:36:55 GMT

A Simple Script - - fix layout

←Older revision		Revision as of 19:36, 27 September 2006
Line 161:		Line 161:

	''A simple Jabber script''		''A simple Jabber script''
		+	<pre>
		+	#!/usr/bin/perl

-	~~<code>\|#!/usr/bin/perl~~	+	use Net::Jabber qw(Client);
		+	use strict;

-	~~use Net::Jabber qw(Client); use strict~~;	+	# List of addressees for our reminder
		+	our @addressees;

-	~~# List of addressees for our reminder our @addressees;~~ # What we want to	+	# What we want to send
-	~~# send~~ my $reminder = $ARGV[0] or die "No reminder!"; ~~# Connect to our~~	+	my $reminder = $ARGV[0] or die "No reminder!";
-	~~# Jabber server my $c= Net::Jabber::Client->new();~~	+
-	~~# $c->Connect('hostname' => 'yak', 'port' => 5222); #~~	+
-	~~# Authenticate $c->AuthSend('username' => 'reminder', 'password'~~	+
-	~~# => 'secret', 'resource' => 'reminder'); # Set handler to deal~~	+
-	~~# with presence packets that might (will) be pushed # to us (we're not~~	+
-	~~# interested in any other type of packet) $c->SetCallBacks('presence'~~	+
-	~~# => \&handle_presence); # Send out our own presence, and run an~~	+
-	~~# event loop for up to 5 seconds # to catch any packets pushed to us~~	+
-	~~# $c->PresenceSend(); $c->Process(5); # Create a new message with~~	+
-	~~# our reminder text my $m = Net::Jabber::Message->new();~~	+
-	~~# $m->SetBody($reminder); # Send the message to each of the~~	+
-	~~# addressees collected in the # handle_presence() subroutine foreach my~~	+
-	~~# $jid (@addressees) {~~	+

-	$m->~~SetTo~~(~~$jid~~); $c->~~Send~~($m);	+	# Connect to our
		+	# Jabber server
		+	my $c= Net::Jabber::Client->new();
		+	$c->Connect('hostname' => 'yak', 'port' => 5222);

		+	# Authenticate
		+	$c->AuthSend('username' => 'reminder', 'password'=> 'secret', 'resource' => 'reminder');
		+
		+	# Set handler to deal with presence packets that might (will) be pushed
		+	# to us (we're not interested in any other type of packet)
		+	$c->SetCallBacks('presence' => \&handle_presence);
		+
		+	# Send out our own presence, and run an
		+	# event loop for up to 5 seconds
		+	# to catch any packets pushed to us
		+	$c->PresenceSend();
		+	$c->Process(5);
		+
		+	# Create a new message with
		+	# our reminder text
		+	my $m = Net::Jabber::Message->new();
		+	$m->SetBody($reminder);
		+
		+	# Send the message to each of the
		+	# addressees collected in the # handle_presence() subroutine
		+	foreach my $jid (@addressees) {
		+	$m->SetTo($jid); $c->Send($m);
	}		}

-	# Disconnect from the Jabber server and exit $c->Disconnect; exit(0);	+	# Disconnect from the Jabber server and exit
-	~~# # Deal with presence packets sub handle_presence {~~	+	$c->Disconnect;
		+	exit(0);

-	my ($sid, $presence) = @_;	+	# Deal with presence packets
		+	sub handle_presence {
		+	my ($sid, $presence) = @_;

-	# Get the presence my $show = $presence->GetShow() \|\| 'online'; # If	+	# Get the presence
-	# the user is around, add to addressee list push @addressees,	+	my $show = $presence->GetShow() \|\| 'online';
-	# $presence->GetFrom() if $show eq 'online' or $show eq 'chat';</~~code~~>	+	# If the user is around, add to addressee list push @addressees,
		+	$presence->GetFrom() if $show eq 'online' or $show eq 'chat';
		+	}
		+	</pre>

-	~~} }}~~ The script is fairly self-explanatory. For now, we'll leave the	+	The script is fairly self-explanatory. For now, we'll leave the
-	~~} }}~~ script's description to the comments embedded within it; by the end	+	script's description to the comments embedded within it; by the end
-	~~} }}~~ of the book, you should have a good understanding of how to put	+	of the book, you should have a good understanding of how to put
-	~~} }}~~ together complete applications and utilities using Jabber libraries	+	together complete applications and utilities using Jabber libraries
-	~~} }}~~ in Perl, Python, and Java.	+	in Perl, Python, and Java.

KruegerN: /* Imaginary Jabber Conversation */

KruegerN — Wed, 27 Sep 2006 19:19:20 GMT

Imaginary Jabber Conversation

(Difference between revisions)

KruegerN: /* Introducing Jabber */ - fix layout

KruegerN — Wed, 27 Sep 2006 18:25:00 GMT

Introducing Jabber - - fix layout

←Older revision		Revision as of 18:25, 27 September 2006
Line 3:		Line 3:
	<br>		<br>
	==Introducing Jabber==		==Introducing Jabber==
-	~~<br>~~This book is about Jabber: the technology, protocols, ideas, and the	+	This book is about Jabber: the technology, protocols, ideas, and the philosophy. Jabber is about connecting things (users, applications, and so on) in an all-pervasive message plasma that flows between clients and servers, carrying content, structure, and conversations.
-	philosophy. Jabber is about connecting things (users, applications, and	+
-	so on) in an all-pervasive message plasma that flows between clients and	+
-	servers, carrying content, structure, and conversations. ~~<br>~~	+

-	The spirit of Jabber lies in its openness, its extensibility, and its	+	The spirit of Jabber lies in its openness, its extensibility, and its lean but generic nature. That it finds itself in the midst of all that technology that will provide the backdrop to the dawn of the next-generation Internet is no accident. ''Web services'', ''peer-to-peer'', ''XML encapsulation'', ''presence'', ''identity'', ''distributed computing'' — these are all phrases that describe key intiatives and developments that lie at the core of the coming transition, and Jabber can and does play a central role.
-	lean but generic nature. That it finds itself in the midst of all that	+
-	technology that will provide the backdrop to the dawn of the	+	This book will show you how Jabber works, what makes it tick, and how to bend and shape it into solutions that join applications and users together. This first part is a guide to Jabber's technology and server. Part II is an examination of Jabber's building blocks and a series of scenarios and scripts we call "recipes," to show you how to deploy Jabber in a variety of situations.
-	next-generation Internet is no accident. Web services, peer-to-peer, XML	+
-	encapsulation, presence, identity, distributed ~~computing—these~~ are all	+
-	phrases that describe key intiatives and developments that lie at the	+
-	core of the coming transition, and Jabber can and does play a central	+
-	role.	+

-	This book will show you how Jabber works, what makes it tick, and how to
-	bend and shape it into solutions that join applications and users
-	together. This first part is a guide to Jabber's technology and server.
-	Part II is an examination of Jabber's building blocks and a series of
-	scenarios and scripts we call "recipes," to show you how to deploy
-	Jabber in a variety of situations.
-	<br>
	==Imaginary Jabber Conversation==		==Imaginary Jabber Conversation==
	<br>To help you better understand what transpires during		<br>To help you better understand what transpires during

Mikeh at 17:12, 13 September 2006

Mikeh — Wed, 13 Sep 2006 17:12:50 GMT

Mikeh at 17:10, 13 September 2006

Mikeh — Wed, 13 Sep 2006 17:10:36 GMT

←Older revision		Revision as of 17:10, 13 September 2006
Line 164:		Line 164:
	* There are human and application participants involved in this conversation; Jabber makes no distinction nor holds any prejudice		* There are human and application participants involved in this conversation; Jabber makes no distinction nor holds any prejudice
	against either participant type. <br>		against either participant type. <br>
-	* XML is used effectively to segregate the conversational chunks (Jim's opening gambit, John's	+	* XML is used effectively to segregate the conversational chunks (Jim's opening gambit, John's response, the price alert, and so on) and to structure and identify data within those chunks (the URL for the earnings story, the portfolio information, the conference room invitation). <br>
-	response, the price alert, and so on) and to structure and identify data within those chunks (the URL for the earnings story, the portfolio information, the conference room invitation). <br>	+
	* Conversational strands are kept in context by use of a <tt><thread/></tt> tag, so that Jim and John's clients have a chance to present what's said in an appropriate way. <br>		* Conversational strands are kept in context by use of a <tt><thread/></tt> tag, so that Jim and John's clients have a chance to present what's said in an appropriate way. <br>
-	* Each conversational chunk is a <tt><presence/></tt>, <tt><message/></tt>, or	+	* Each conversational chunk is a <tt><presence/></tt>, <tt><message/></tt>, or <tt><iq/></tt> tag—the three Jabber building blocks on which everything is based. <br>
-	<tt><iq/></tt> tag—the three Jabber building blocks on which everything is based. <br>	+	* The conversation takes place across two Jabber servers; one server is located at <tt>company-a.com</tt> and the other at <tt>company-b.com</tt>.
-	* The conversation takes place across two Jabber servers; one server is located at <tt>company-a.com</tt> and the	+	* The conversation flow is asynchronous, in the sense that out of nowhere, a message alerting John to a stock price fall below threshold appears seemingly in the middle of John's conversation with Jim, as does the message from the ''workassist'' agent. <br>
-	other at <tt>company-b.com</tt>.	+
-	* The conversation flow is asynchronous, in the sense that out of nowhere, a message alerting John	+
-	to a stock price fall below threshold appears seemingly in the middle of John's conversation with Jim, as does the message from the	+
-	''workassist'' agent. <br>	+
	* All Jabber entities, human or otherwise, are identified by Jabber IDs such as John's (<tt>john@company-a.com</tt>) or the stock alert mechanism (<tt>alert@stocks.company-b.com</tt>). <br>		* All Jabber entities, human or otherwise, are identified by Jabber IDs such as John's (<tt>john@company-a.com</tt>) or the stock alert mechanism (<tt>alert@stocks.company-b.com</tt>). <br>
	* <tt>company-b.com</tt>'s stock system is multifaceted. As well as being able to send (and receive settings for) threshold alerts through the <tt>alert@stocks.company-b.com</tt> address, it can also interact using different identities to reflect the context of the stock being discussed. For example, <tt>MEGC@stocks.company-b.com</tt> represents the Megacorp (MEGC) stock.<br>		* <tt>company-b.com</tt>'s stock system is multifaceted. As well as being able to send (and receive settings for) threshold alerts through the <tt>alert@stocks.company-b.com</tt> address, it can also interact using different identities to reflect the context of the stock being discussed. For example, <tt>MEGC@stocks.company-b.com</tt> represents the Megacorp (MEGC) stock.<br>

Mikeh: /* Imaginary Jabber Conversation */

Mikeh — Wed, 13 Sep 2006 17:09:18 GMT

Imaginary Jabber Conversation

←Older revision		Revision as of 17:09, 13 September 2006
Line 162:		Line 162:
	conversation:		conversation:

-	* There are human and application participants involved in this	+	* There are human and application participants involved in this conversation; Jabber makes no distinction nor holds any prejudice
-	conversation; Jabber makes no distinction nor holds any prejudice	+
	against either participant type. <br>		against either participant type. <br>
-	* XML is used effectively to	+	* XML is used effectively to segregate the conversational chunks (Jim's opening gambit, John's
-	segregate the conversational chunks (Jim's opening gambit, John's	+	response, the price alert, and so on) and to structure and identify data within those chunks (the URL for the earnings story, the portfolio information, the conference room invitation). <br>
-	response, the price alert, and so on) and to structure and identify data	+	* Conversational strands are kept in context by use of a <tt><thread/></tt> tag, so that Jim and John's clients have a chance to present what's said in an appropriate way. <br>
-	within those chunks (the URL for the earnings story, the portfolio	+	* Each conversational chunk is a <tt><presence/></tt>, <tt><message/></tt>, or
-	information, the conference room invitation). <br>	+	<tt><iq/></tt> tag—the three Jabber building blocks on which everything is based. <br>
-	* Conversational strands	+	* The conversation takes place across two Jabber servers; one server is located at <tt>company-a.com</tt> and the
-	are kept in context by use of a <tt><thread/></tt> tag, so that	+
-	Jim and John's clients have a chance to present what's said in an	+
-	appropriate way. <br>	+
-	* Each conversational chunk is a	+
-	<tt><presence/></tt>, <tt><message/></tt>, or	+
-	<tt><iq/></tt> tag—the three Jabber building blocks on which	+
-	everything is based. <br>	+
-	* The conversation takes place across two	+
-	Jabber servers; one server is located at <tt>company-a.com</tt> and the	+
	other at <tt>company-b.com</tt>.		other at <tt>company-b.com</tt>.
-	* The conversation flow is	+	* The conversation flow is asynchronous, in the sense that out of nowhere, a message alerting John
-	asynchronous, in the sense that out of nowhere, a message alerting John	+	to a stock price fall below threshold appears seemingly in the middle of John's conversation with Jim, as does the message from the
-	to a stock price fall below threshold appears seemingly in the middle of	+
-	John's conversation with Jim, as does the message from the	+
	''workassist'' agent. <br>		''workassist'' agent. <br>
-	* All Jabber entities, human or otherwise,	+	* All Jabber entities, human or otherwise, are identified by Jabber IDs such as John's (<tt>john@company-a.com</tt>) or the stock alert mechanism (<tt>alert@stocks.company-b.com</tt>). <br>
-	are identified by Jabber IDs such as John's	+	* <tt>company-b.com</tt>'s stock system is multifaceted. As well as being able to send (and receive settings for) threshold alerts through the <tt>alert@stocks.company-b.com</tt> address, it can also interact using different identities to reflect the context of the stock being discussed. For example, <tt>MEGC@stocks.company-b.com</tt> represents the Megacorp (MEGC) stock.<br>
-	(<tt>john@company-a.com</tt>) or the stock alert mechanism	+	* In fact, this stock system is a Jabber component, a single entity that takes on each of the stock guises in the
-	(<tt>alert@stocks.company-b.com</tt>).	+	conversation. <br>
-	* <tt>company-b.com</tt>'s stock	+	The most common misconception about Jabber is that it's solely for instant messaging—Jabber is more than a bridge to other IM systems or a set of protocols. Instant messaging is just one of countless ways that an XML-based messaging technology such as Jabber's can be applied. Jabber is an extensible client/server architecture that ''routes'' XML data between clients and ''services'', which plug into Jabber servers as ''components''. The original and core set of components provide the IM features (and supporting services) that were briefly described in the Preface.<br>
-	system is multifaceted. As well as being able to send (and receive	+
-	settings for) threshold alerts through the	+
-	<tt>alert@stocks.company-b.com</tt> address, it can also interact using	+
-	different identities to reflect the context of the stock being	+
-	discussed. For example, <tt>MEGC@stocks.company-b.com</tt> represents	+
-	the Megacorp (MEGC) stock.<br>	+
-	* In fact, this stock system is a Jabber	+
-	component, a single entity that takes on each of the stock guises in the	+
-	conversation. The most common misconception about Jabber is that it's	+
-	solely for instant messaging—Jabber is more than a bridge to other IM	+
-	systems or a set of protocols. Instant messaging is just one of	+
-	countless ways that an XML-based messaging technology such as Jabber's	+
-	can be applied. Jabber is an extensible client/server architecture that	+
-	''routes'' XML data between clients and ''services'', which plug into	+
-	Jabber servers as ''components''. The original and core set of	+
-	components provide the IM features (and supporting services) that were	+
-	briefly described in the Preface.<br>	+

	The XML structures that make up the Jabber protocol fall into three		The XML structures that make up the Jabber protocol fall into three

Mikeh: /* Introducing Jabber */

Mikeh — Wed, 13 Sep 2006 17:05:53 GMT

Introducing Jabber

←Older revision		Revision as of 17:05, 13 September 2006
Line 23:		Line 23:
	scenarios and scripts we call "recipes," to show you how to deploy		scenarios and scripts we call "recipes," to show you how to deploy
	Jabber in a variety of situations.		Jabber in a variety of situations.
-	<br> ==Imaginary Jabber Conversation==	+	<br>
		+	==Imaginary Jabber Conversation==
	<br>To help you better understand what transpires during		<br>To help you better understand what transpires during
	a Jabber-based conversation, this section presents a conversation		a Jabber-based conversation, this section presents a conversation

←Older revision		Revision as of 03:12, 7 January 2009
Line 1:		Line 1:
		+	cbolitroclac
	{{Content Programming Jabber}}		{{Content Programming Jabber}}
	=Getting Started with Jabber=		=Getting Started with Jabber=
Line 4:		Line 5:
	This book is about Jabber: the technology, protocols, ideas, and the philosophy. Jabber is about connecting things (users, applications, and so on) in an all-pervasive message plasma that flows between clients and servers, carrying content, structure, and conversations.		This book is about Jabber: the technology, protocols, ideas, and the philosophy. Jabber is about connecting things (users, applications, and so on) in an all-pervasive message plasma that flows between clients and servers, carrying content, structure, and conversations.

-	The spirit of Jabber lies in its openness, its extensibility, and its lean but generic nature. That it finds itself in the midst of all that technology that will provide the backdrop to the dawn of the next-generation Internet is no accident. ''Web services'', ''peer-to-peer'', ''XML encapsulation'', ''presence'', ''identity'', ''distributed computing'' — these are all phrases that describe key intiatives and developments that lie at the core of the coming transition, and Jabber can and does play a central role.	+	The spirit of Jabber lies in its openness, its extensibility, and its lean but generic nature. That it finds itself in the midst of all that technology that will provide the backdrop to the dawn of the next-generation Internet is no accident. ''Web services'', ''peer-to-peer'', ''XML encapsulation'', ''presence'', ''identity'', ''distributed computing'' â these are all phrases that describe key intiatives and developments that lie at the core of the coming transition, and Jabber can and does play a central role.

	This book will show you how Jabber works, what makes it tick, and how to bend and shape it into solutions that join applications and users together. This first part is a guide to Jabber's technology and server. Part II is an examination of Jabber's building blocks and a series of scenarios and scripts we call "recipes," to show you how to deploy Jabber in a variety of situations.		This book will show you how Jabber works, what makes it tick, and how to bend and shape it into solutions that join applications and users together. This first part is a guide to Jabber's technology and server. Part II is an examination of Jabber's building blocks and a series of scenarios and scripts we call "recipes," to show you how to deploy Jabber in a variety of situations.
Line 124:		Line 125:
	* XML is used effectively to segregate the conversational chunks (Jim's opening gambit, John's response, the price alert, and so on) and to structure and identify data within those chunks (the URL for the earnings story, the portfolio information, the conference room invitation).		* XML is used effectively to segregate the conversational chunks (Jim's opening gambit, John's response, the price alert, and so on) and to structure and identify data within those chunks (the URL for the earnings story, the portfolio information, the conference room invitation).
	* Conversational strands are kept in context by use of a <tt><thread/></tt> tag, so that Jim and John's clients have a chance to present what's said in an appropriate way.		* Conversational strands are kept in context by use of a <tt><thread/></tt> tag, so that Jim and John's clients have a chance to present what's said in an appropriate way.
-	* Each conversational chunk is a <tt><presence/></tt>, <tt><message/></tt>, or <tt><iq/></tt> ~~tag—the~~ three Jabber building blocks on which everything is based.	+	* Each conversational chunk is a <tt><presence/></tt>, <tt><message/></tt>, or <tt><iq/></tt> tagâthe three Jabber building blocks on which everything is based.
	* The conversation takes place across two Jabber servers; one server is located at <tt>company-a.com</tt> and the other at <tt>company-b.com</tt>.		* The conversation takes place across two Jabber servers; one server is located at <tt>company-a.com</tt> and the other at <tt>company-b.com</tt>.
	* The conversation flow is asynchronous, in the sense that out of nowhere, a message alerting John to a stock price fall below threshold appears seemingly in the middle of John's conversation with Jim, as does the message from the ''workassist'' agent.		* The conversation flow is asynchronous, in the sense that out of nowhere, a message alerting John to a stock price fall below threshold appears seemingly in the middle of John's conversation with Jim, as does the message from the ''workassist'' agent.
Line 131:		Line 132:
	* In fact, this stock system is a Jabber component, a single entity that takes on each of the stock guises in the conversation.		* In fact, this stock system is a Jabber component, a single entity that takes on each of the stock guises in the conversation.

-	The most common misconception about Jabber is that it's solely for instant ~~messaging—Jabber~~ is more than a bridge to other IM systems or a set of protocols. Instant messaging is just one of countless ways that an XML-based messaging technology such as Jabber's can be applied. Jabber is an extensible client/server architecture that ''routes'' XML data between clients and ''services'', which plug into Jabber servers as ''components''. The original and core set of components provide the IM features (and supporting services) that were briefly described in the Preface.	+	The most common misconception about Jabber is that it's solely for instant messagingâJabber is more than a bridge to other IM systems or a set of protocols. Instant messaging is just one of countless ways that an XML-based messaging technology such as Jabber's can be applied. Jabber is an extensible client/server architecture that ''routes'' XML data between clients and ''services'', which plug into Jabber servers as ''components''. The original and core set of components provide the IM features (and supporting services) that were briefly described in the Preface.

	The XML structures that make up the Jabber protocol fall into three		The XML structures that make up the Jabber protocol fall into three
Line 155:		Line 156:
	Jabber-related functions such as handling the connection to the server		Jabber-related functions such as handling the connection to the server
	(this is via another library that <tt>Net::Jabber</tt>		(this is via another library that <tt>Net::Jabber</tt>
-	~~uses—~~<tt>XML::Stream</tt>), authentication, events, and all the	+	usesâ<tt>XML::Stream</tt>), authentication, events, and all the
	mechanisms to parse and create Jabber traffic.		mechanisms to parse and create Jabber traffic.

←Older revision		Revision as of 17:12, 13 September 2006
Line 11:		Line 11:
	lean but generic nature. That it finds itself in the midst of all that		lean but generic nature. That it finds itself in the midst of all that
	technology that will provide the backdrop to the dawn of the		technology that will provide the backdrop to the dawn of the
-	next-generation Internet is no accident. Web services, peer-to-peer, XML	+	next-generation Internet is no accident. Web services, peer-to-peer, XML
	encapsulation, presence, identity, distributed computing—these are all		encapsulation, presence, identity, distributed computing—these are all
	phrases that describe key intiatives and developments that lie at the		phrases that describe key intiatives and developments that lie at the
Line 210:		Line 210:
	use Net::Jabber qw(Client); use strict;		use Net::Jabber qw(Client); use strict;

-	# List of addressees for our reminder our @addressees; # What we want to	+	# List of addressees for our reminder our @addressees; # What we want to
-	# send my $reminder = $ARGV[0] or die "No reminder!"; # Connect to our	+	# send my $reminder = $ARGV[0] or die "No reminder!"; # Connect to our
-	# Jabber server my $c= Net::Jabber::Client->new();	+	# Jabber server my $c= Net::Jabber::Client->new();
-	# $c->Connect('hostname' => 'yak', 'port' => 5222); #	+	# $c->Connect('hostname' => 'yak', 'port' => 5222); #
-	# Authenticate $c->AuthSend('username' => 'reminder', 'password'	+	# Authenticate $c->AuthSend('username' => 'reminder', 'password'
-	# => 'secret', 'resource' => 'reminder'); # Set handler to deal	+	# => 'secret', 'resource' => 'reminder'); # Set handler to deal
-	# with presence packets that might (will) be pushed # to us (we're not	+	# with presence packets that might (will) be pushed # to us (we're not
-	# interested in any other type of packet) $c->SetCallBacks('presence'	+	# interested in any other type of packet) $c->SetCallBacks('presence'
-	# => \&handle_presence); # Send out our own presence, and run an	+	# => \&handle_presence); # Send out our own presence, and run an
-	# event loop for up to 5 seconds # to catch any packets pushed to us	+	# event loop for up to 5 seconds # to catch any packets pushed to us
-	# $c->PresenceSend(); $c->Process(5); # Create a new message with	+	# $c->PresenceSend(); $c->Process(5); # Create a new message with
-	# our reminder text my $m = Net::Jabber::Message->new();	+	# our reminder text my $m = Net::Jabber::Message->new();
-	# $m->SetBody($reminder); # Send the message to each of the	+	# $m->SetBody($reminder); # Send the message to each of the
-	# addressees collected in the # handle_presence() subroutine foreach my	+	# addressees collected in the # handle_presence() subroutine foreach my
-	# $jid (@addressees) {	+	# $jid (@addressees) {

	$m->SetTo($jid); $c->Send($m);		$m->SetTo($jid); $c->Send($m);
Line 230:		Line 230:
	}		}

-	# Disconnect from the Jabber server and exit $c->Disconnect; exit(0);	+	# Disconnect from the Jabber server and exit $c->Disconnect; exit(0);
-	# # Deal with presence packets sub handle_presence {	+	# # Deal with presence packets sub handle_presence {

	my ($sid, $presence) = @_;		my ($sid, $presence) = @_;

-	# Get the presence my $show = $presence->GetShow() \|\| 'online'; # If	+	# Get the presence my $show = $presence->GetShow() \|\| 'online'; # If
-	# the user is around, add to addressee list push @addressees,	+	# the user is around, add to addressee list push @addressees,
-	# $presence->GetFrom() if $show eq 'online' or $show eq 'chat';</code>	+	# $presence->GetFrom() if $show eq 'online' or $show eq 'chat';</code>

	} }} The script is fairly self-explanatory. For now, we'll leave the		} }} The script is fairly self-explanatory. For now, we'll leave the