View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001290 | unreal | ircd | public | 2003-10-03 11:07 | 2003-10-04 01:02 |
| Reporter | fez | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta18 | ||||
| Summary | 0001290: /stats and /who sendqueues | ||||
| Description | It would be nice if unreal handled /stats G and /who's similarly to the way it handles /list, so that the user requesting it doesn't get disconnected for sendq exceeded. (I already increased the sendqueue in my class {} block but it still exceeds) Thanks - fez | ||||
| 3rd party modules | |||||
|
|
Well you have to be very careful with these things... One of the basic things with IRC (well, locally) is that all output is synchronized (not sure if that's the right word, but nothing happends in-between).. I'll try to explain :p. Usually you get a "snapshot", like with /who now and /names, etc... if one would send a little bit of the current state every time things may have changed in-between.. Like: you do a /who #chan, but half-way someone parts or someone else joins, that's horrible (you could miss them). /list also has this, but this isn't much of a problem... that's just a channel listing, if someone created a new channel while you were doing /list you could miss it but who cares... also you can receive other traffic during the /list, that's why it doesn't stall. [Example: <- :maintest.test.net 322 Ein #qgjlapopk 1 : <- :maintest.test.net 322 Ein #bjgpuqlatxkr 1 : <- :[email protected] PRIVMSG #flood :aaaaaaaaaaa[etc] <- :[email protected] PRIVMSG #flood :aaaaaaaaaaaaaa[etc] <- :maintest.test.net 322 Ein #mbckftocw 1 : ] So it would be very bad for /who... Maybe for /stats it could be done, but stats is really something for ircops IMO, so why not put your opers in an oper class and give them like 4Mb sendq ? On a sidenote, codemastr is working on limiting the amount of /who output to XXX(X) lines (well not for /who #chan, but for /who *, /who *.nl, etc) [Reason I give this long reply is because it has been suggested before :p] edited on: 10-03-03 14:43 |
|
|
Yeah, imho something like this needs support on the client's end to fully work. As for /stats, that's why the new advanced searching system was added. You can set it to only send you the stuff you want. /stats G +mr *@*.aol.com *clones* That would return only bans matching *@*.aol.com who have clones in the reason. If you take advantage of the searching features, I don't see it causing much of a problem. |
