Line endings in ServerQuery - \n\r instead of \r\n

[St4Lk3R]

Hey there,

I hope I'm posting in the right section of this forum... I didn't yet run my ServerQuery tests against a Windows or Mac Teamspeak 3 server, so for now I hope I am.

I just noticed while trying to do some ServerQuery programming that the line endings used there are in fact \n\r. This isn't used by any operating system (Windows: \r\n, Mac: \r, Linux: \n), so I'd like to ask if there is a specific reason for the line endings being like this.

These \n\r line endings are a bit bothersome when trying to parse the line endings with PHP. It ain't impossible, but if it can be fixed, I'd be all for it

Best regards,
Stalker

[PatrickW]

Actually this is a really nice (simple but amazing) way to differ between single ServerQuery responses (such as error id=0 msg=ok) and multi-line texts that are however to be treated as a single ServerQuery response.

So help returns a text with \r\n as multi-line separator, terminates that response with \n\r, sends the error response terminating with \n\r.

I like it, because that way responses are much easier to separate, and I would like to keep it like that

[maggy]

So basically, you're saying it really isn't a bug and it really is a feature. :P

[PatrickW]

Yes, exactly