JabChapter 4 - Revision history

KruegerN: insert content template

2006-10-07T10:08:15Z

insert content template

←Older revision		Revision as of 10:08, 7 October 2006
Line 1:		Line 1:
	<br>		<br>
		+	{{Content Programming Jabber}}
	=Server Architecture and Configuration=		=Server Architecture and Configuration=
	<br>If you followed Chapter 3 through, you		<br>If you followed Chapter 3 through, you

Mikeh: /* "Real" Virtual Jabber Servers */

2006-09-14T03:33:27Z

"Real" Virtual Jabber Servers

←Older revision		Revision as of 03:33, 14 September 2006
Line 3,392:		Line 3,392:


-	{{Note\|Don't forget that you can use two <tt>xdb</tt> component	+	<big> Note: </big>Don't forget that you can use two <tt>xdb</tt> component
	instances, specifying a different host filter in each, to store data in		instances, specifying a different host filter in each, to store data in
	separate places--see Section 4.5 earlier in this chapter.		separate places--see Section 4.5 earlier in this chapter.

-	}}	+
	They also share the same <tt>io</tt> settings and <tt>pidfile</tt>		They also share the same <tt>io</tt> settings and <tt>pidfile</tt>
	definition; after all, there is still only one Jabber server that is		definition; after all, there is still only one Jabber server that is
Line 3,613:		Line 3,613:

	<br>		<br>
		+
	===Splitting Up Jabber Server Processes ===		===Splitting Up Jabber Server Processes ===
	<br>As well as being able to		<br>As well as being able to

Mikeh: /* Server Constellations */

2006-09-14T03:32:49Z

Server Constellations

←Older revision		Revision as of 03:32, 14 September 2006
Line 3,301:		Line 3,301:

	<big> Note: </big>If the Hostname Resolution component is configured to run, then		<big> Note: </big>If the Hostname Resolution component is configured to run, then
-	you will see two processes at startup, as the	+	you will see two processes at startup, as the component--<tt>dnsrv</tt>--forks to have the resolver functionality run in
-	component--<tt>dnsrv</tt>--forks to have the resolver functionality run in	+	a separate child process.
-	a separate child process.}}	+
	<br>		<br>
-	In this concluding section of this chapter, we take a look at some of	+	In this concluding section of this chapter, we take a look at some of the possible constellations and how they're constructed.
-	the possible constellations and how they're constructed.	+

Mikeh: /* Server Constellations */

2006-09-14T03:32:05Z

Server Constellations

←Older revision		Revision as of 03:32, 14 September 2006
Line 3,300:		Line 3,300:


-	{{Note\|If the Hostname Resolution component is configured to run, then	+	<big> Note: </big>If the Hostname Resolution component is configured to run, then
	you will see two processes at startup, as the		you will see two processes at startup, as the
	component--<tt>dnsrv</tt>--forks to have the resolver functionality run in		component--<tt>dnsrv</tt>--forks to have the resolver functionality run in

Mikeh: /* Filter service */

2006-09-14T03:30:59Z

Filter service

←Older revision		Revision as of 03:30, 14 September 2006
Line 1,073:		Line 1,073:


-	[[image:jab_0407.png\|A message filter\|center\|350 px]] ~~Each~~	+	[[image:jab_0407.png\|A message filter\|center\|350 px]]
-	user's filter is stored on the server using the xdb component (see	+	<br> Each user's filter is stored on the server using the xdb component (see
	later). What does a typical filter look like? Well, Example 4-9 shows a		later). What does a typical filter look like? Well, Example 4-9 shows a
	filter that contains two rules:		filter that contains two rules:

Mikeh: /* Custom Configuration */

2006-09-14T03:29:03Z

Custom Configuration

←Older revision		Revision as of 03:29, 14 September 2006
Line 2,856:		Line 2,856:
	: Karma is used in the <tt>s2s</tt> component to control connection		: Karma is used in the <tt>s2s</tt> component to control connection
	: traffic, just as it is used in <tt>c2s</tt>. See Section 4.13 later in		: traffic, just as it is used in <tt>c2s</tt>. See Section 4.13 later in
-	: this chapter for more details.	+	: this chapter for more details. <br>
-	{{Sidebar\|DialbackWhen an external Jabber server requests a connection	+	<big>Sidebar: </big>DialbackWhen an external Jabber server requests a connection
	to your Jabber server, the dialback mechanism ensures that the external		to your Jabber server, the dialback mechanism ensures that the external
	Jabber server's identification can be verified. This is to prevent		Jabber server's identification can be verified. This is to prevent
Line 2,869:		Line 2,869:


-	~~{{Figure~~\|~~title=~~Dialback in action\|~~image=0596002025-jab_0416.png}} Based~~	+	[[image:jab_0416.png\|Dialback in action\|center\|350 px]]
-	on the validity of the key, your Jabber server can accept or refuse the	+	<br> Based on the validity of the key, your Jabber server can accept or refuse the
	incoming connection from the external Jabber server.		incoming connection from the external Jabber server.

Line 2,877:		Line 2,877:
	connection.		connection.

-	}}

	<br>		<br>

Mikeh: /* Custom Configuration */

2006-09-14T03:27:21Z

Custom Configuration

←Older revision		Revision as of 03:27, 14 September 2006
Line 2,831:		Line 2,831:


-	{{Note\|As the namespace for the exchange of document streams in a	+	<big>Note: </big>As the namespace for the exchange of document streams in a
	client-to-server connection is <tt>jabber:client</tt>, so the namespace		client-to-server connection is <tt>jabber:client</tt>, so the namespace
	for the exchange of document streams in a server-to-server connection is		for the exchange of document streams in a server-to-server connection is
	<tt>jabber:server</tt>.		<tt>jabber:server</tt>.

-	}}	+
	There are three immediate child tags in the configuration wrapper tag:		There are three immediate child tags in the configuration wrapper tag:

Line 2,880:		Line 2,880:

	<br>		<br>
		+
	===Component Connection Method ===		===Component Connection Method ===
	<br>The library load method is used to		<br>The library load method is used to

Mikeh: /* Host Filter */

2006-09-14T03:26:50Z

Host Filter

←Older revision		Revision as of 03:26, 14 September 2006
Line 1,894:		Line 1,894:


-	{{Sidebar\|To <ns/> or Not to <ns/>If you are going to use	+	<big>Sidebar: </big>To <ns/> or Not to <ns/>If you are going to use
	namespace filters for <tt>xdb</tt> components, make sure you specify		namespace filters for <tt>xdb</tt> components, make sure you specify
	them for ''every''<tt>xdb</tt> component instance definition; otherwise,		them for ''every''<tt>xdb</tt> component instance definition; otherwise,
Line 1,900:		Line 1,900:
	be incorrect and your Jabber server will not start.		be incorrect and your Jabber server will not start.

-	}}

	<br>		<br>
		+
	===Custom Configuration ===		===Custom Configuration ===
	<br>The custom configuration section in our		<br>The custom configuration section in our

Mikeh: /* Browsable service information */

2006-09-14T03:26:18Z

Browsable service information

←Older revision		Revision as of 03:26, 14 September 2006
Line 1,628:		Line 1,628:


-	{{Note\|Note also that the <tt><browse/></tt> section can list	+	<big>Note: </big>Note also that the <tt><browse/></tt> section can list
	services that are ''not'' local to the Jabber server in which that		services that are ''not'' local to the Jabber server in which that
	<tt><browse/></tt> section occurs. See Section 4.16.4 for details.		<tt><browse/></tt> section occurs. See Section 4.16.4 for details.

-	}}

	<br>		<br>

Mikeh: /* Autoupdate of JUD */

2006-09-14T03:25:18Z

Autoupdate of JUD

←Older revision		Revision as of 03:25, 14 September 2006
Line 1,540:		Line 1,540:


-	{{Note\|The JUD is referred to here as a "local" JUD because there's a	+	<big>Note: </big>The JUD is referred to here as a "local" JUD because there's a
	central JUD running on jabber.org that every Jabber user can connect to		central JUD running on jabber.org that every Jabber user can connect to
	and use (even if they're on a different Jabber server); the word "local"		and use (even if they're on a different Jabber server); the word "local"
	makes the distinction that the JUD is running locally to the Jabber		makes the distinction that the JUD is running locally to the Jabber
	server to which the Jabber user is connected.		server to which the Jabber user is connected.
-		+	<br>
-	}}	+
	If you're not running a JUD locally, or you simply don't want your		If you're not running a JUD locally, or you simply don't want your
	users' vCard updates going to a JUD, you can safely comment this tag		users' vCard updates going to a JUD, you can safely comment this tag