projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices Coding] TS3/4 Support | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20TS3/4%20Support&In-Reply-To="> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="001816.html"> | |
| 11 | <LINK REL="Next" HREF="001818.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] TS3/4 Support</H1> | |
| 15 | <B>Chris Plant</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20TS3/4%20Support&In-Reply-To=" | |
| 17 | TITLE="[IRCServices Coding] TS3/4 Support">chris at monkeyircd.org | |
| 18 | </A><BR> | |
| 19 | <I>Sun Dec 29 03:50:14 PST 2002</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="001816.html">[IRCServices Coding] Idea for akills | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="001818.html">[IRCServices Coding] bahamut/Services crash | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#1817">[ date ]</a> | |
| 27 | <a href="thread.html#1817">[ thread ]</a> | |
| 28 | <a href="subject.html#1817">[ subject ]</a> | |
| 29 | <a href="author.html#1817">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>Hello | |
| 35 | ||
| 36 | I'm working on monkeyircd's protocol module for services, and I've hit a | |
| 37 | problem. | |
| 38 | As I understand it, in TS3 mode, when services loses its link/shuts | |
| 39 | down, it should send/receive QUITs for all the clients it handles. But | |
| 40 | in TS4 mode it just receives a SQUIT for the link lost, and then should | |
| 41 | calculate the QUITs and SQUITs that follow as a consequence. | |
| 42 | ||
| 43 | How hard would it be to change the protocol module to either of these | |
| 44 | behaviours (I suspect the former would be easier). MonkeyIRCD handles | |
| 45 | both behaviours, as specified in the TS4 protocol, by using either | |
| 46 | TS3/TS4 as declared at the start of a server link session. | |
| 47 | ||
| 48 | Chris | |
| 49 | ||
| 50 | ||
| 51 | </PRE> | |
| 52 | ||
| 53 | <!--endarticle--> | |
| 54 | <HR> | |
| 55 | <P><UL> | |
| 56 | <!--threads--> | |
| 57 | <LI>Previous message: <A HREF="001816.html">[IRCServices Coding] Idea for akills | |
| 58 | </A></li> | |
| 59 | <LI>Next message: <A HREF="001818.html">[IRCServices Coding] bahamut/Services crash | |
| 60 | </A></li> | |
| 61 | <LI> <B>Messages sorted by:</B> | |
| 62 | <a href="date.html#1817">[ date ]</a> | |
| 63 | <a href="thread.html#1817">[ thread ]</a> | |
| 64 | <a href="subject.html#1817">[ subject ]</a> | |
| 65 | <a href="author.html#1817">[ author ]</a> | |
| 66 | </LI> | |
| 67 | </UL> | |
| 68 | ||
| 69 | </body></html> |