#Irc client registration#
#Irc client software#

#Irc client software#

What they provide depends entirely on the software packages being run.ДЄ trend these days is to hide the real structure of a network from regular users. вЂServicesвЂ™ themselves are not specified in any way by the protocol, they are different from the services defined by the RFCs.

#Irc client registration#

Features usually handled by services include client account registration (as are typically used for SASL authentication), channel registration (allowing client accounts to вЂownвЂ™ channels), and further modifications and extensions to the IRC protocol. Services are not used on all networks, and the capabilities typically provided by them may be built-into server software itself rather than being provided by a separate software package. Services: A вЂservicesвЂ™ server is a special type of server that extends the capabilities of the server software on the network (ie, they provide services to the network).In the figure above, Servers 7, 8, 10, 13, 14, and others would be considered leaf servers. Typically, leafs are the primary servers that handle client connections. Leaf: A вЂleafвЂ™ is a server that is only connected to a single other server on the network.

For instance, in the figure above, Server 1, Server 2, and Server 3 may be considered core hubs by the network administrators. What is considered a core hub will change depending on the size of a network and what the administrators of the network consider important.

Core Hub: A вЂcore hubвЂ™ is typically a hub server that connects fairly major parts of the IRC network together.

For instance, in the figure above, Server 2, Server 3, and Server 4 would be examples of hub servers.

Hub: A вЂhubвЂ™ is a server that connects to multiple other servers.

Some of the most common terms are as follows: There have been several terms created over time to describe the roles of different servers on an IRC network. Other topologies are being experimented with, but right now there are none widely used in production. The most common network configuration for IRC servers is that of a spanning tree, where each server acts as a central node for the rest of the network it sees. Servers form the backbone of IRC, providing a point to which clients may connect and talk to each other, and a point for other servers to connect to, forming an IRC network. This section goes through each of those, what they are and a brief overview of them. ArchitecturalДЄ typical IRC network consists of servers and clients connected to those servers, with a good mix of IRC operators and channels. This section describes concepts behind the implementation and organisation of the IRC protocol, which are useful in understanding how it works. The key words вЂњMUSTвЂќ, вЂњMUST NOTвЂќ, вЂњREQUIREDвЂќ, вЂњSHALLвЂќ, вЂњSHALL NOTвЂќ, вЂњSHOULDвЂќ, вЂњSHOULD NOTвЂќ, вЂњRECOMMENDEDвЂќ, вЂњMAYвЂќ, and вЂњOPTIONALвЂќ in this document are to be interpreted as described in RFC2119. Messages are delivered through this network and state is maintained across it for the connected clients and active channels. A typical setup involves multiple servers connected in a distributed network. It is well-suited to running on many machines in a distributed fashion.

IRC is a text-based chat protocol which has proven itself valuable and useful. This document describes the IRC Client-Server protocol. The Internet Relay Chat (IRC) protocol has been designed over a number of years, with multitudes of implementations and use cases appearing.