[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2001 / 000008.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices Coding] Services 5
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205&In-Reply-To=">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="000006.html">
   <LINK REL="Next"  HREF="000013.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices Coding] Services 5</H1>
    <B>Mark Hetherington</B> 
    <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205&In-Reply-To="
       TITLE="[IRCServices Coding] Services 5">mark at mhetherington.demon.co.uk
       </A><BR>
    <I>Thu Dec 13 14:42:45 PST 2001</I>
    <P><UL>
        <LI>Previous message: <A HREF="000006.html">[IRCServices Coding] ChanServ Question
</A></li>
        <LI>Next message: <A HREF="000013.html">[IRCServices Coding] Services 5
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#8">[ date ]</a>
              <a href="thread.html#8">[ thread ]</a>
              <a href="subject.html#8">[ subject ]</a>
              <a href="author.html#8">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Firstly, thanks to Andrew for releasing the alpha version. Hopefully he will
not feel that he has to later remove this opportunity.

A few early questions that maybe Andrew or the Alpha team might be able to
comment on.

1) Do we have any idea on time scale for development beyond alpha? I
understand that it is a difficult question to answer given RL committments
but based on work so far and this extended open test hopefully highlighting
major issues quite quickly, might make it easier to provide an estimate.

2) Despite the warning not to run the alpha on a production network, it does
seem to be the best place to run it since it will give a much more realistic
test of the code. It is also very tempting to upgrade :) To this end, are
there specific known issues at this time with the current build that would
make it completely impractical to run on a small production network? The
&quot;knownbugs&quot; file does not seem to have anything specific to Services 5 and
nothing serious mentioned either way but those who have already had chance
to play with Services 5 may have a good idea of things that would make it
unsuitable for risking in a production environment.

3) At present we seem to be restricted to the mailing list for bug reporting
and discussion which makes the process qyute closed. Has there been any
thought given to providing some kind of online tracking system which would
both show what bugs are currently known and their status? Maybe something on
sourceforge or similar system would suffice.

4) I was wondering about the reasons for AJOIN being included in Services 5.
It seems to place an overhead on NickServ that has been handled by many IRC
clients for a number of years. Even clients which do not specifically
support it, but that implement perform can easily provide AJOIN
functionality. Any client supporting scripting could easily manage an AJOIN
list. A number of clients support dynamic AJOIN lists by offering to
remember hannels that a user uses on a regular basis.

Since part of the ethos behind IRC Services development is not to perform
tasks that really belong in IRCd or in clients or could be scripted, it
seems odd that firstly this system has been implemented and secondly it is
enabled in a default configuration.

Is there something specific that I am missing about this services managed
auto join list which makes it preferable to the existing client code which
already performs this task?


Anyway, back to play around with the source some more.

Mark.


</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="000006.html">[IRCServices Coding] ChanServ Question
</A></li>
	<LI>Next message: <A HREF="000013.html">[IRCServices Coding] Services 5
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#8">[ date ]</a>
              <a href="thread.html#8">[ thread ]</a>
              <a href="subject.html#8">[ subject ]</a>
              <a href="author.html#8">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices Coding] Services 5
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205&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="000006.html">
	11	<LINK REL="Next" HREF="000013.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices Coding] Services 5</H1>
	15	<B>Mark Hetherington</B>
	16	<A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205&In-Reply-To="
	17	TITLE="[IRCServices Coding] Services 5">mark at mhetherington.demon.co.uk
	18	</A><BR>
	19	<I>Thu Dec 13 14:42:45 PST 2001</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="000006.html">[IRCServices Coding] ChanServ Question
	22	</A></li>
	23	<LI>Next message: <A HREF="000013.html">[IRCServices Coding] Services 5
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#8">[ date ]</a>
	27	<a href="thread.html#8">[ thread ]</a>
	28	<a href="subject.html#8">[ subject ]</a>
	29	<a href="author.html#8">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>Firstly, thanks to Andrew for releasing the alpha version. Hopefully he will
	35	not feel that he has to later remove this opportunity.
	36
	37	A few early questions that maybe Andrew or the Alpha team might be able to
	38	comment on.
	39
	40	1) Do we have any idea on time scale for development beyond alpha? I
	41	understand that it is a difficult question to answer given RL committments
	42	but based on work so far and this extended open test hopefully highlighting
	43	major issues quite quickly, might make it easier to provide an estimate.
	44
	45	2) Despite the warning not to run the alpha on a production network, it does
	46	seem to be the best place to run it since it will give a much more realistic
	47	test of the code. It is also very tempting to upgrade :) To this end, are
	48	there specific known issues at this time with the current build that would
	49	make it completely impractical to run on a small production network? The
	50	"knownbugs" file does not seem to have anything specific to Services 5 and
	51	nothing serious mentioned either way but those who have already had chance
	52	to play with Services 5 may have a good idea of things that would make it
	53	unsuitable for risking in a production environment.
	54
	55	3) At present we seem to be restricted to the mailing list for bug reporting
	56	and discussion which makes the process qyute closed. Has there been any
	57	thought given to providing some kind of online tracking system which would
	58	both show what bugs are currently known and their status? Maybe something on
	59	sourceforge or similar system would suffice.
	60
	61	4) I was wondering about the reasons for AJOIN being included in Services 5.
	62	It seems to place an overhead on NickServ that has been handled by many IRC
	63	clients for a number of years. Even clients which do not specifically
	64	support it, but that implement perform can easily provide AJOIN
65	functionality. Any client supporting scripting could easily manage an AJOIN
66	list. A number of clients support dynamic AJOIN lists by offering to
67	remember hannels that a user uses on a regular basis.
68
69	Since part of the ethos behind IRC Services development is not to perform
70	tasks that really belong in IRCd or in clients or could be scripted, it
71	seems odd that firstly this system has been implemented and secondly it is
72	enabled in a default configuration.
73
74	Is there something specific that I am missing about this services managed
75	auto join list which makes it preferable to the existing client code which
76	already performs this task?
77
78
79	Anyway, back to play around with the source some more.
80
81	Mark.
82
83
84	</PRE>
85
86	<!--endarticle-->
87	<HR>
88	<P><UL>
89	<!--threads-->
90	<LI>Previous message: <A HREF="000006.html">[IRCServices Coding] ChanServ Question
91	</A></li>
92	<LI>Next message: <A HREF="000013.html">[IRCServices Coding] Services 5
93	</A></li>
94	<LI> <B>Messages sorted by:</B>
95	<a href="date.html#8">[ date ]</a>
96	<a href="thread.html#8">[ thread ]</a>
97	<a href="subject.html#8">[ subject ]</a>
98	<a href="author.html#8">[ author ]</a>
99	</LI>
100	</UL>
101
102	</body></html>