]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] JOIN 0 subject | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20JOIN%200%20subject&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="000094.html"> | |
11 | <LINK REL="Next" HREF="000139.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] JOIN 0 subject</H1> | |
15 | <B>Pinto, Joao Luis (J.)</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20JOIN%200%20subject&In-Reply-To=" | |
17 | TITLE="[IRCServices] JOIN 0 subject">jpinto9 at visteon.com | |
18 | </A><BR> | |
19 | <I>Thu Sep 23 04:46:27 PDT 1999</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="000094.html">[IRCServices] JOIN 0 subject | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="000139.html">[IRCServices] JOIN 0 subject | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#95">[ date ]</a> | |
27 | <a href="thread.html#95">[ thread ]</a> | |
28 | <a href="subject.html#95">[ subject ]</a> | |
29 | <a href="author.html#95">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Thanks, I would like just to fix the URL: is <A HREF="http://www.ptlink.net...">http://www.ptlink.net...</A> and | |
35 | not plink.net. | |
36 | ||
37 | I would like to know if there is any intention to implement TOKEN protocol | |
38 | on services, since most of dalnet based ircd's support TOKEN protocol | |
39 | reducing network bandwidth usage. | |
40 | ||
41 | Another thing I would like to know is any ideas how to implement services | |
42 | registration/query from a web page, I know some networks support this, what | |
43 | do you think with be the best way to do this, via a services BOT getting | |
44 | messages from a Java applet connected to the IRC network or by coding a | |
45 | socket listener directly on services to manage this. I don't have to many | |
46 | experience on this, so please if someone have some ideas or some code about | |
47 | his I would appreciate that. | |
48 | ||
49 | ---- | |
50 | I don't see a problem with postings like this so long as they don't get | |
51 | out of hand and are related to the IRC Services this list is for. However, | |
52 | problems associated with any 3rd party code will not be supported by this | |
53 | list. | |
54 | ||
55 | Andrew | |
56 | ||
57 | On Thu, 23 Sep 1999, Pinto, Joao Luis (J.) wrote: | |
58 | ||
59 | ><i> I removed JOIN 0 support from my ircd, my network runs with 10 servers, I | |
60 | </I>am | |
61 | ><i> running services for 5 months, I have a 1600 nicks registered on 5 months | |
62 | </I>><i> and I dint found any JOIN 0 unknown messages from any client, besides | |
63 | </I>those | |
64 | ><i> I used to test it :) | |
65 | </I>><i> On large network probably if removing is going to be wiped out should be | |
66 | </I>><i> using firs bye a ircd version that would just accept JOIN 0 from servers, | |
67 | </I>><i> not client and finally when all network upgrade, all JOIN 0 support could | |
68 | </I>be | |
69 | ><i> removed. | |
70 | </I>><i> Off curse on a distribution point of view for services I agreed they | |
71 | </I>should | |
72 | ><i> support JOIN 0 for ircd compatibility. | |
73 | </I>><i> I would like to publish the URL from my services, that I expect not to be | |
74 | </I>><i> considered as SPAM, I am publishing it here as a source of code to be | |
75 | </I>><i> applied on Andy Church services by anyone interested in some of the | |
76 | </I>><i> features, if you think this is not very wise, or breaks the subject of | |
77 | </I>this | |
78 | ><i> ML please let me know, in that case I will not do this again. My new | |
79 | </I>version | |
80 | ><i> of services: 1.2.0 available from <A HREF="<A HREF="http://www.plink.net/Coders/index.html"">http://www.plink.net/Coders/index.html"</A>><A HREF="http://www.plink.net/Coders/index.html</A">http://www.plink.net/Coders/index.html</A</A>> | |
81 | </I>><i> addresses some problems I think still exist on actual services. | |
82 | </I>><i> | |
83 | </I>><i> P.S.: Sorry, about my english :) | |
84 | </I>><i> | |
85 | </I>><i> João Luís Marques Pinto | |
86 | </I>><i> PTlink Tech - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">Lamego at PTlink.net</A> | |
87 | </I>><i> <A HREF="<A HREF="http://www.PTlink.net"">http://www.PTlink.net"</A>><A HREF="http://www.PTlink.net</A">http://www.PTlink.net</A</A>> | |
88 | </I>><i> | |
89 | </I>><i> | |
90 | </I>--------------------------------------------------------------- | |
91 | To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A> | |
92 | with "unsubscribe ircservices" in the body, without the quotes. | |
93 | ||
94 | </PRE> | |
95 | ||
96 | <!--endarticle--> | |
97 | <HR> | |
98 | <P><UL> | |
99 | <!--threads--> | |
100 | <LI>Previous message: <A HREF="000094.html">[IRCServices] JOIN 0 subject | |
101 | </A></li> | |
102 | <LI>Next message: <A HREF="000139.html">[IRCServices] JOIN 0 subject | |
103 | </A></li> | |
104 | <LI> <B>Messages sorted by:</B> | |
105 | <a href="date.html#95">[ date ]</a> | |
106 | <a href="thread.html#95">[ thread ]</a> | |
107 | <a href="subject.html#95">[ subject ]</a> | |
108 | <a href="author.html#95">[ author ]</a> | |
109 | </LI> | |
110 | </UL> | |
111 | ||
112 | </body></html> |