home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!destroyer!sol.ctr.columbia.edu!spool.mu.edu!carroll1!dprust
- From: dprust@carroll1.cc.edu (Dan Prust)
- Newsgroups: alt.irc
- Subject: Re: /summon command?
- Message-ID: <3294@carroll1.cc.edu>
- Date: 30 Aug 92 02:27:54 GMT
- Article-I.D.: carroll1.3294
- References: <1992Aug9.013000.15607@newshost.anu.edu.au> <BspC1J.7r0@ux1.cso.uiuc.edu> <26522@life.ai.mit.edu>
- Organization: Carroll College-Waukesha, WI
- Lines: 29
-
- In article <26522@life.ai.mit.edu> gwydion@hal.gnu.ai.mit.edu (Lord of the Third Truth) writes:
- >In article <BspC1J.7r0@ux1.cso.uiuc.edu> Upholder@uiuc.edu (THE Upholder of Truth) writes:
- >>well, here's a radical idea, have /summon check the CLIENTS connected from
- >>a specific host and use the CLIENT instead of the server to issue the
- >>actual /summon.
- >
- >*ungh*
-
- Wait a second, call me crazy, but if their client is running... why /summon?
- Seems to me that if you want to be radical, issue a /summon command and have
- it get the host name. Exactly what is wrong (or so damn hard) with using
- another of the ports (extensive number of which can be used) to run a seperate
- summoning program? It wouldn't be hard at all to write, really. Have the
- client extract the name from nickserv and send a message to summon this person,
- if logged in. I'd write it, but I'm trying to learn C++ right now, and don't
- have the time. Besides. I don't know my way around the client that well.
- I don't spend much time on IRC. But you elite coderz, if you are truly
- elite, write a simple program to listen through a port like 6668. WHY must
- we limit it to 6667?
-
- If a person doesn't have this summon daemon running, then you can't summon
- them. Very simple.
-
- Hell, the program would be small. A small hack in the server code, a
- small hack in the client code, and a small program to listen and summon.
-
- Sheesh.
- ---------- -------- -------- ------- ------ ----- --- -- - - - - -
- Daniel Allen Prust dprust@carroll1.cc.edu
-