Comment #5 on issue 381 by dorma...@rydia.net: Incomplete command does not
result in ERROR response
https://code.google.com/p/memcached/issues/detail?id=381
It's not really built to do half-close situations I think... if it detects
that it just blows out.
That might be the wrong thing to do in some situations I guess. I'll give
it some more thought. We do have the quit command, and since it's a
request/response protocol the client is supposed to wait until it receives
an END before dc'ing. This doesn't work well with echo and netcat but isn't
generally a problem with real clients.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to memcached+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
