X-Git-Url: http://git.pk910.de/?a=blobdiff_plain;f=doc%2Fp10.html;h=fbbc4fe82fd1070295130e093343f2f76d847204;hb=refs%2Fheads%2Fupstream-ssl;hp=9bedbc89d7cc682e5d4385a808c74af4a0c4c0b5;hpb=448cf2696162129b24174ea625684984378322aa;p=ircu2.10.12-pk.git diff --git a/doc/p10.html b/doc/p10.html index 9bedbc8..fbbc4fe 100644 --- a/doc/p10.html +++ b/doc/p10.html @@ -2,17 +2,17 @@
- +
After the connection has been established and verified, the next step @@ -637,7 +665,8 @@ the originally recieved server message, with the only exception being that the message is numeric prefixed, to indicate which server sent this message (and also therefore, which hub this new server is linked too). There is also a fixed "0" present before the Description field, this is a placeholder -for future use and currently unused. +for future use and currently unused. [Isomer: Question, what IS this +reserved for?]
3.2.2 - NICK Messages
Client information is transmitted via "NICK" messages, of the @@ -680,7 +709,8 @@ the "Host" part of the user@host mask.[Optional]: User modes. If present, this is always +<user modes -for this client>. +for this client>. Note that the special +r usermode is followed by the +client's account name; see the documentation for ACCOUNT.The real IP address of this client, a Base64 encoded 32bit int. @@ -800,14 +830,21 @@ line would be:
3.2.4 - JUPE Messages-
Any currently unexpired JUPEs are transmitted via "JUPE" -messages with the following format:+
Any currently unexpired JUPEs are transmitted via "JUPE" messages +with the following format:
--[NUMERIC PREFIX] JU * (+|-)[SERVER NAME] -[LIFETIME] [LAST MOD] :[REASON]-
Notes:+
[NUMERIC PREFIX] JU * (+|-)[SERVER +NAME] [LIFETIME] [LAST MOD] :[REASON]+For example: + +
+1 2 3 4 +5 6 +7 ++Notes:
AZ JU * +juped.undernet.org 000003593 955419707 +:Juped Server
The following table summarises the sequence of events that occur when
a server connects to another server. S1 is our server, and S2 is a HUB
@@ -889,7 +924,206 @@ the END_OF_BURST from S2
[Back] +
This chapter provides details of the messages that can be sent after +successfully linking to a network, and synchronising the channel/user database. +
4.1 Channel state operations +
There are a number of messages that can modify the state of a channel, +these are: +
The MODE message can modify channel modes and bans, and also give or +take operator/voice status from channel members. +
For Example:
+
Notes:
+
+
Token | + +Function | + +Parameters | +
p | + +Sets/Unsets 'Private' Flag. | + +None. | +
s | + +Sets/Unsets 'Secret' Flag. | + +None. | +
m | + +Sets/Unsets 'Moderated' Flag. | + +None. | +
n | + +Sets/Unsets 'External Messages' Flag. | + +None. | +
t | + +Sets/Unsets 'Topic Limit' Flag. | + +None. | +
i | + +Sets/Unsets 'Invite only' Flag. | + +None. | +
l | + +Sets/Unsets 'Channel Limit' Flag. | + +The channel limit. | +
k | + +Sets/Unsets 'Channel Key' Flag. | + +The channel keyword (Password). | +
o | + +Ops and Deops users. | + +Numeric of user to be opped. | +
v | + +Voice | + +Numeric of user to be voiced. | +
b | + +Ban | + +Ban string. | +
N.B: The "MODE" message is also used to modify a client's user modes,
+not just channel modes. See section 4.2 for details.
The OPMODE message is identical in syntax to the MODE message, however +it will only ever have an operator as the source. It is likely that the +source of this mode will not have ops in the target channel, but it should +succeed never the less. +
4.1.3 - JOIN +
4.1.4 - PART +
4.1.5 - KICK +
4.1.6 - TOPIC +
4.1.7 - CLEARMODE
+
+
4.2.1 - NICK ++4.3 Channel/Client Messaging. +AZAAA N Nick2 955423230+4.2.2 - MODE +AZAAA M Nick2 :+odi+4.2.3 - ACCOUNT +AX AC AZAAA oper+The ACCOUNT message provides a way for servers, such as the channel service +server, to set the account name information that is associated with a client. +Once set, it cannot be unset or changed, and will be propagated in NICK during +net bursts using the special user mode +r followed by the account name. +
4.3.1 - PRIVMSG ++[Back]4.3.2 - NOTICE +
4.3.3 - CNOTICE +
4.3.4 - CPRIVMSG +
5. Programmers reference: Client/Server
@@ -913,14 +1147,20 @@ A. ...
[20/01/2000]: Initial draft, structure, background info.
- [2000-01-20]: Initial draft, structure, background info.
+
[13/02/2000]: Added initial BURST documentation.
-
[14/02/2000]: Continued BURST documentation / Begin NICK and SERVER
+
[2000-02-13]: Added initial BURST documentation.
+
[2000-02-14]: Continued BURST documentation / Begin NICK and SERVER
documentation.
-
[26/02/2000]: Continued chapter 5, few example fixes, added token table
-from msg.h. --Gte.
-
[02/03/2000]: Added NICK spec. --Gte.
-
[18/03/2000]: Added JUPE spec. -Kev
+
[2000-02-26]: Continued chapter 5, few example fixes, added token table
+from msg.h. -Gte.
+
[2000-03-02]: Added NICK spec. -Gte.
+
[2000-03-18]: Added JUPE spec. -Kev
+
[2000-04-10]: Added information about OPMODE and CLEARMODE tokens.
+-Kev
+
[2000-04-11]: Started work on chapter 4. -Gte
+
[2000-06-01]: Changed some info about the max number of clients -Isomer
+
[2002-01-11]: Wrote a specification for ACCOUNT and noted that a usermode
+in a NICK message may have an argument. -Kev
[Back]