ping
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | ping [2006/08/29 16:08] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | # $EPIC: ping.txt,v 1.2 2006/08/19 03:58:07 sthalik Exp $ | ||
| + | ======Synopsis: | ||
| + | __ping__ < | ||
| + | __ping__ < | ||
| + | |||
| + | ======Description: | ||
| + | Lag is a way of life on irc. " | ||
| + | a message to get from the sender to the recipient. | ||
| + | it takes for someone to get your messages. | ||
| + | how long it will take for a message to get to someone else and back. The | ||
| + | __PING__ command sends someone a specially crafted message asking them to | ||
| + | send the message back. When you receive the message back, you can then | ||
| + | measure the amount of time it took to come back and that will tell you how | ||
| + | much lag there is to that person. | ||
| + | |||
| + | This command uses the [[CTCP]] [[ctcp PING|ping]] command to do its work. | ||
| + | |||
| + | This command actually sends a message to the other person who will then | ||
| + | send another message back. If the server (or network) is already overloaded | ||
| + | with traffic, this will only add to the burden. | ||
| + | will make the lag worse, so be reasonable. | ||
| + | |||
| + | Not every client will respond to a PING request. | ||
| + | to receive a reply to a PING command. | ||
| + | request rendering the results invalid. | ||
| + | an accurate reply to a PING command. | ||
| + | |||
| + | The PING command uses the [[CTCP]] command and so will not work from within an | ||
| + | /[[ON MSG]], /[[ON PUBLIC]], /[[ON PUBLIC_OTHER]], | ||
| + | |||
| + | ======Examples: | ||
| + | To see how far away your friend booya is from you: | ||
| + | /ping booya | ||
| + | |||
| + | To see how far away everyone in channel #blah is: | ||
| + | /ping #blah | ||
ping.txt · Last modified: 2006/08/29 16:08 by 127.0.0.1
