| 1 |
$eterna: ircio,v 1.2 2001/08/12 15:42:27 mrg Exp $ |
| 2 |
|
| 3 |
ircio is part of this distribution. |
| 4 |
You can set whether you want to install it within the Makefile, |
| 5 |
here's a little help in deciding: |
| 6 |
|
| 7 |
Pros: |
| 8 |
IRCII will run as two separate processes, with ircio responding to server |
| 9 |
PINGs. This means you can stop IRCII (with ^Z) and not get disconnected |
| 10 |
from a server. It will buffer 4K of stuff before it blocks and PINGs |
| 11 |
will be missed. If, for some reason, the ircio program cannot be |
| 12 |
started, IRCII will connect directly to the server without it |
| 13 |
(transparently to the user) |
| 14 |
|
| 15 |
Cons: |
| 16 |
It blocks beyond 4K of stuff. |
| 17 |
While being smaller than IRCII, it still takes up disk space. |
| 18 |
Since it runs as a separate process, it uses system resources while |
| 19 |
running (although not much). |
| 20 |
|
| 21 |
Note: If you add #define NON_BLOCKING to ircio.c, then ircio will |
| 22 |
not block at all. Rather, it will discard all info beyond the 4K. |
| 23 |
This means it will never miss a PING. |
| 24 |
It can, however, screw up certain things (such as NOTIFY) if some |
| 25 |
of the return information is discarded. Use this NON_BLOCKING at |
| 26 |
your own discretion |
| 27 |
|
| 28 |
Operation of IRCII is identical either way. Remember to do a |
| 29 |
"make installserv" to compile and install ircio if you are using it. |