Protocols/MSNP/Commands/OUT: Difference between revisions
No edit summary |
Animadoria (talk | contribs) No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Protocols/MSNP}} | |||
= OUT = | = OUT = | ||
== Notification Server == | == Notification Server == | ||
Latest revision as of 18:44, 11 May 2022
| MSNP Protocol |
| Introduction • Terms • Clients |
| Reference |
| Error List • Commands • Relying Party Suite • Spotlife |
| Services |
| XMPP • HTTP Gateway • Tabs • Activities |
| Documentation |
| Development Tools • MSNP Grid |
| Polygamy • URLs used by MSN |
| Documents |
| Protocol Versions |
| Version 21 |
| Version 18 |
| Version 16 |
| Version 15 |
| Version 14 |
| Version 13 |
| Version 12 |
| Version 11 |
| Version 9 |
| Version 8 |
| Version 2 |
| MSNC |
| Introduction • P2P • Object Descriptor • Display Pictures • File Transfer |
| Scenarios |
| Microsoft Messenger for Mac |
| MSNP on WebTV (MSNTV) |
OUT
Notification Server
From Client
Sent to notification server upon leaving. No transaction ID is sent.
>>> OUT <<< OUT
The server will reply with an echo before closing the connection. Clients do not need to send the OUT command, but it is recommended. Simply closing the connection will have the same effect.
Asynchronously
The server may send an OUT to clients asynchronously, usually with a parameter
<<< OUT reason
Where reason is OTH if the user has logged on from another location (if the service does not support multiple simultaneous connections) or SSD if the notification server is being taking down for maintenance, in which case the client should reconnect to a dispatch server to get an XFR to another notification server.
Switchboard Server
Sent to switchboard upon leaving.
Sending it isn't necessary, you can just close the connection. The syntax for having the server close the connection (gracefully) is:
OUT\r\n