Support both forms of ISON as clients seem to send one and the RFC mandates another:

ISON nick1 nick2 nick3,
or
ISON :nick1 nick2 nick3.
Interestingly this means we now even support:   ISON nick1 nick2 :nick3 nick4


git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@6465 e03df62e-2008-0410-955e-edbf42e46eb7

1 files changed, 29 insertions, 0 deletions

diff --git a/src/cmd_ison.cpp b/src/cmd_ison.cpp
index f89b549ca..9f415e7fb 100644
--- a/src/cmd_ison.cpp
+++ b/src/cmd_ison.cpp
@@ -44,6 +44,35 @@ CmdResult cmd_ison::Handle (const char** parameters, int pcnt, userrec *user)
 			}
 			ison_already[u] = u;
 		}
+		else
+		{
+			if ((i == pcnt-1) && (strchr(parameters[i],' ')))
+			{
+				/* Its a space seperated list of nicks (RFC1459 says to support this)
+				 */
+				irc::spacesepstream list(parameters[i]);
+				std::string item = "*";
+				while (((item = list.GetToken()) != ""))
+				{
+					u = ServerInstance->FindNick(parameters[i]);
+					if (ison_already.find(u) != ison_already.end())
+						continue;
+
+					if (u)
+					{
+						reply.append(u->nick).append(" ");
+						if (reply.length() > 450)
+						{
+							user->WriteServ(reply);
+							reply = std::string("303 ") + user->nick + " :";
+						}
+						ison_already[u] = u;
+					}
+				}
+			}
+			/* There will only be one of these, we can bail after. */
+			break;
+		}
 	}
 
 	if (!reply.empty())