Databases
StackOverflow2013
Postsdbo
POPHP - IRC "QUIT" not working properly
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPHP - IRC "QUIT" not working properly
    primarykey
    data
    text
    <p><strong>CHANGE:</strong> I have determined the problem has nothing to do with the coding. However the problem stays still, as this appears to be caused by IRC, I'm still in search of the reason.</p> <p>The server I'm connecting uses two kinds of PING requests:</p> <p>One is asked upon connecting to server, and it's in format of alpha-numeric values of 8 characters. </p> <p>Example: <code>PING :EA0E9275.</code></p> <p>And another one is after the server sends out MOTD, joins channels, completes "End of /NAMES list". Then after "n delay" server sends me a ping request with current connected host as it's value. </p> <p>Example: <code>PING :irc.ams.nl.euirc.net</code></p> <p>If I send the command "QUIT :Quit Message" before I reply the host PING request, server ignores the QUIT message, and instead, it quits with a server-filled status message similiar to "Client Exited" message.</p> <p>Example: <code>ERROR :Closing Link: Nick[IP.ADD.RE.SS] (Life is too short...)</code></p> <p>However if I send the same command after responding to host PING request, my QUIT gets processed as it should.</p> <p>Example: <code>ERROR :Closing Link: Nick[IP.ADD.RE.SS] (Quit: Quit Message)</code></p> <p>I've checked in the RFC, and found this on QUIT section:</p> <p><em>If, for some other reason, a client connection is closed without the client issuing a QUIT command (e.g. client dies and EOF occurs on socket), the server is required to fill in the quit message with some sort of message reflecting the nature of the event which caused it to happen.</em></p> <p>Also, if still in need to see the partial code I'm using to accomplish this, <a href="http://pastebin.com/2EZigTUY" rel="nofollow">you can check it here</a>. However, this is a common issue with mIRC the IRC client.</p> <p><strong>Basic scheme</strong></p> <ul> <li>Connecting to server... <ul> <li>Connected!</li> <li>Server waiting NICK/USER info...</li> <li>Server received NICK/USER info, waiting for alphanumeric PING reply... <ul> <li>Server received alphanumeric PING reply, sending MOTD.</li> <li>End of MOTD, sending JOIN to join channels...</li> <li>Joined to channels, NAMES list for channels have been requested.</li> <li>End of NAMES list.</li> </ul></li> <li>Receiving active channel(s)/server data. <ul> <li>If sent QUIT command, server will ignore the usual QUIT, and will send "Closing Link" by server default as status quit(Life is too short...).</li> </ul></li> <li>Server is doing an alive-check, received host PING(irc.ams.nl.euirc.net), server is waiting reply... <ul> <li>Sent server the reply.</li> <li>If sent QUIT command, server will process QUIT command as user-level, the usual way, and will send "Closing Link" by user-specified message or empty.((QUIT: User Message) or (QUIT: ))</li> </ul></li> </ul></li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKetchup God
    1. USKetchup God
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload