Mercurial > dovecot > original-hg > dovecot-1.2

comparison doc/auth-protocol.txt @ 4800:f24a1e1c8310 HEAD

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Removed "DIE" command from auth protocol. It wasn't implemented, and I'm not sure if it's such a good idea anyway.
author Timo Sirainen <tss@iki.fi>
date Sun, 12 Nov 2006 21:54:26 +0200
parents bc071307fc2a
children 40ce533c88f9
comparison
equal deleted inserted replaced
4799:84058cf85f90 4800:f24a1e1c8310
148 Master Requests 148 Master Requests
149 --------------- 149 ---------------
150 150
151 M: "REQUEST" TAB <id> TAB <client-pid> TAB <client-id> 151 M: "REQUEST" TAB <id> TAB <client-pid> TAB <client-id>
152 M: "USER" TAB <id> TAB <userid> TAB service=<service> [TAB <parameters>] 152 M: "USER" TAB <id> TAB <userid> TAB service=<service> [TAB <parameters>]
153 M: "DIE"
154 153
155 S: "NOTFOUND" TAB <id> 154 S: "NOTFOUND" TAB <id>
156 S: "FAIL" TAB <id> TAB <error message> 155 S: "FAIL" TAB <id> TAB <error message>
157 S: "USER" TAB <id> TAB <userid> [TAB <parameters>] 156 S: "USER" TAB <id> TAB <userid> [TAB <parameters>]
158 157
162 USER command's service and parameters are the same as with AUTH client 161 USER command's service and parameters are the same as with AUTH client
163 request. 162 request.
164 163
165 ID is a connection-specific unique request identifier. It must be a 32bit 164 ID is a connection-specific unique request identifier. It must be a 32bit
166 number, so typically you'd just increment it by one. 165 number, so typically you'd just increment it by one.
167
168 DIE makes the server stop accepting new requests, and as soon as the
169 existing requests are finished, it kills itself.
170 166
171 NOTFOUND reply means that the request or user wasn't found. Master 167 NOTFOUND reply means that the request or user wasn't found. Master
172 shouldn't even try to send REQUEST commands for nonexisting requests, so if 168 shouldn't even try to send REQUEST commands for nonexisting requests, so if
173 it happens it means either a timeout caused by very high load, or client 169 it happens it means either a timeout caused by very high load, or client
174 lying to master about the request. 170 lying to master about the request.