Permalink
Browse files

Fixed contradition re. quit command in protocol doc.

The diff excluding changes to wordwrapping is:

-There is no command to close the connection -- the client may
+The client may issue the "quit" command, or
  • Loading branch information...
1 parent a744711 commit 75c5269dc2e749752c549ca27a4782b8d87f4479 @pda pda committed Oct 12, 2009
Showing with 5 additions and 5 deletions.
  1. +5 −5 doc/protocol.txt
View
@@ -23,11 +23,11 @@ sequence of bytes. The server never inspects or modifies a job body and always
sends it back in its original form. It is up to the clients to agree on a
meaningful interpretation of job bodies.
-There is no command to close the connection -- the client may simply close the
-TCP connection when it no longer has use for the server. However, beanstalkd
-performs very well with a large number of open connections, so it is usually
-better for the client to keep its connection open and reuse it as much as
-possible. This also avoids the overhead of establishing new TCP connections.
+The client may issue the "quit" command, or simply close the TCP connection
+when it no longer has use for the server. However, beanstalkd performs very
+well with a large number of open connections, so it is usually better for the
+client to keep its connection open and reuse it as much as possible. This also
+avoids the overhead of establishing new TCP connections.
If a client violates the protocol (such as by sending a request that is not
well-formed or a command that does not exist) or if the server has an error,

0 comments on commit 75c5269

Please sign in to comment.