Delphi-Kylix
  Home arrow Delphi-Kylix arrow Page 3 - IRC Client Theory
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
DELPHI-KYLIX

IRC Client Theory
By: Leidago
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 3
    2007-01-08

    Table of Contents:
  • IRC Client Theory
  • How does IRC work?
  • Operators
  • Channel Operators

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    IRC Client Theory - Operators


    (Page 3 of 4 )

    Because a network can contain many thousands of clients, it stands to reason that there must be someone to moderate or make sure that everything runs smoothly. That is exactly what an operator does. The operators, essentially a special group of clients, are allowed to do general maintenance on a network.

    Operators have powers to connect and disconnect servers as needed "to prevent long-term use of bad network routing." They also have the power to remove a user from the network by force by disconnecting a client from the server. It is debatable whether clients should have this kind of power, but it is definitely needed.

    Channels

    A channel is a named group of clients that converse in the same channel. A channel is created by the first client that joins it and closes down when the last client leaves. Channel names must start with a "&" or "#" symbol with up to 200 characters.  The only restriction on a channel name is that it may not contain any spaces (' '), a control G (^G or ASCII 7), or a comma (',' which is used as a list item separator by the protocol). 

    There are two types of channels allowed by this protocol. One is a distributed channel which is known to all the servers that are connected to the network. The other type of channel is limited to one server, and only clients on the server where it exists may join. These channels are distinguished by a leading '&' character.

    On top of these two types, there are the various channel modes available to alter the characteristics of individual channels. The RFC provides more information on the different MODES. To create or to take part in an existing channel you JOIN the channel. By creating a new channel you automatically become the channel operator. 

    Whether your request to JOIN a particular channel is accepted will depend on the mode of the channel. For example, if you try to join a channel where the mode dictates a limit to the number of users that can join, and you try to join when that limit has been reached, then your request will be refused. Similarly if you try to join a channel that is "invitation only," your request will be rejected unless you are invited. The protocol also states that a user may join up to ten channels simultaneously.

    More Delphi-Kylix Articles
    More By Leidago


       · Any comments on this will be greatly appreciated.
     

    DELPHI-KYLIX ARTICLES

    - Delphi Wrapper Classes and XML
    - Delphi and the DOM
    - Delphi and XML
    - Internet Access: Client Service
    - Finishing the Client for an Internet Access ...
    - The Client for an Internet Access Control Ap...
    - User Management for an Internet Access Contr...
    - Important Procedures for an Internet Access ...
    - Server Code for an Internet Access Control A...
    - Constructing the Interface for an Internet A...
    - Building a Server Application for an Interne...
    - Building an Internet Access Control Applicat...
    - Client Dataset: Working with Data Packets an...
    - Using the Client Dataset in an N-Tiered Appl...
    - Using the Client Dataset in Two-Tiered Clien...






    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 3 hosted by Hostway
    Stay green...Green IT