Memcached advocacy
Yo, http://code.google.com/p/memcached/wiki/Advocacy mostly stolen from: http://wiki.postgresql.org/wiki/BoothCheckList http://wiki.postgresql.org/wiki/AdvocacyGuides Back in july-ish Brian attempted to start this conversation. Lets finish it. I'll be putting in all of the notes I feel are fair to the project, and were useful to me as someone who has organized booths. If you are a commercial entity and wish to perform advocacy with us or for us, *please* respond to this thread with your thoughts. *Please* be constructive. We've been waiting to hear from you folks for a long time. The last few conventions were turbulent, to say the least. With the addition of these pages this should be completely avoidable in the future. If you're *not* commercial folk and would be interested in helping advocate memcached in conferences far and wide, please help us flesh out these rules and tips. Thanks, -Dormando
Re: opaque vs request id ( in binary udp protocol )
About the usage of the opaque field: For my Erlang Memcached client (binary protocol only) I send multiple requests in batch over one TCP connection. I use the opaque field as a requestid; when I receive responses back from the server, I lookup those opaque values in a table and send the replies to whoever sent the command. This makes it possible to for example deduplicate requests and have silent requests that return no data (because when Memcached sends a response, I know all sequence ids before that were apparantly not interesting - thus silent)
Re: Issue 105 in memcached: curr_items stats seem wrong
Comment #2 on issue 105 by CMPTuOMP3: curr_items stats seem wrong http://code.google.com/p/memcached/issues/detail?id=105 Thanks for the clarification. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
