| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame^] | 1 | SYNOPSIS |
| 2 | int logon (void) |
| 3 | int logon (int flag) |
| 4 | |
| 5 | DESCRIPTION |
| 6 | When the driver created a new connection (either by accepting |
| 7 | it or by creating it with net_connect()) and bound it to an |
| 8 | object, it then calls logon() in that object. |
| 9 | |
| 10 | The method should return 0 on failure, and everything else on |
| 11 | success. |
| 12 | |
| 13 | If the driver attempted to create a connection in the |
| 14 | background and failed, it will call logon(-1) in the intended |
| 15 | object to inform the mudlib about the failure. |
| 16 | |
| 17 | If the master attempted a secure connection in connect(E) and |
| 18 | did not set an explicit TLS callback, the call to logon() won't |
| 19 | happen until the TLS handshake is complete. If the master set |
| 20 | a TLS callback, that will be executed in place of logon(). |
| 21 | |
| 22 | HISTORY |
| 23 | LDMud 3.2.10 added the extended meaning for net_connect(). |
| 24 | LDMud 3.2.13/3.3.713 streamlined the handling of secure connections |
| 25 | during logon. |
| 26 | |
| 27 | SEE ALSO |
| 28 | connect(M), net_connect(E), exec(E), tls_init_connection(E) |