On Sun, Mar 09, 2003 at 08:06:37PM +0100, [EMAIL PROTECTED] wrote:
> Sorry, command seperator is \r\n. :/
SEPARATOR
> --
> volta
>
> +++ GMX - Mail, Messaging & more http://www.gmx.net +++
> Bitte l?cheln! Fotogalerie online mit GMX ohne eigene Homepage!
- db
also note, that officially the command names should be in ALL CAP's (ie
NICK and USER) regardless of the fact that most servers will accept the
lowercase version thereof.
On Monday, Mar 10, 2003, at 06:11 Pacific/Auckland, [EMAIL PROTECTED] wrote:
I strongly suggest reading the rfc1459:
End of
> I strongly suggest reading the rfc1459:
> End of command is \n\r and not \n\n;
I assume you mean "\r\n"--nobody uses "\n\r"
--
Kevin L. Mitchell <[EMAIL PROTECTED]>
Sorry, command seperator is \r\n. :/
> I strongly suggest reading the rfc1459:
> End of command is \n\r and not \n\n;
> The fullname in USER should be prefixed with : to indicate, that it's the
> last parameter.
> PHP issues:
> Strings are not prefixed and sufixed with an escaped doublequote,
> ""
I strongly suggest reading the rfc1459:
End of command is \n\r and not \n\n;
The fullname in USER should be prefixed with : to indicate, that it's the
last parameter.
PHP issues:
Strings are not prefixed and sufixed with an escaped doublequote, ""
is enough.
> Hello;
> in one of my php document i
Hello;
in one of my php document i am using this parameters and about this parameters, i need
raw`s \"user\" command`s parameters on undernet server. If u send me that parameters i
will be very happy. My computer has more than one statical ip and i want to use one of
them so i need this paramete
> Is the * character allowed in channel names? I thought such characters were
> not?
Why wouldn't it be? IRCU prohibits control characters, but pretty much
everything else is accepted, except for comma (,), space, and non-breaking
space.
--
Kevin L. Mitchell <[EMAIL PROTECTED]>
