memcache服务器端

  • i5_681674
    了解作者
  • 90.2KB
    文件大小
  • zip
    文件格式
  • 0
    收藏次数
  • VIP专享
    资源类型
  • 0
    下载次数
  • 2022-04-01 04:00
    上传日期
memcache服务器端 版本:1.2.1 安装方法:在cmd下,切换到解压目录,执行以下命令 memcached.exe -k install memcached.exe -k start 即可。以后每次开机,会自动作为服务启动,不需要的话,自己去服务中关闭自动启动
memcached-1.2.1-win32.zip
  • doc
  • memory_management.txt
    4.9KB
  • OSX.txt
    846B
  • memcached.1
    3.2KB
  • protocol.txt
    17KB
  • Makefile.am
    46B
  • CONTRIBUTORS.txt
    795B
  • LICENSE
    1.5KB
  • COPYING
    1.5KB
  • memcached.exe
    152KB
  • README
    737B
  • NEWS
    41B
  • AUTHORS
    71B
  • CONTRIBUTORS
    1.3KB
内容介绍
Protocol -------- Clients of memcached communicate with server through TCP connections. (A UDP interface is also available; details are below under "UDP protocol.") A given running memcached server listens on some (configurable) port; clients connect to that port, send commands to the server, read responses, and eventually close the connection. There is no need to send any command to end the session. A client may just close the connection at any moment it no longer needs it. Note, however, that clients are encouraged to cache their connections rather than reopen them every time they need to store or retrieve data. This is because memcached is especially designed to work very efficiently with a very large number (many hundreds, more than a thousand if necessary) of open connections. Caching connections will eliminate the overhead associated with establishing a TCP connection (the overhead of preparing for a new connection on the server side is insignificant compared to this). There are two kinds of data sent in the memcache protocol: text lines and unstructured data. Text lines are used for commands from clients and responses from servers. Unstructured data is sent when a client wants to store or retrieve data. The server will transmit back unstructured data in exactly the same way it received it, as a byte stream. The server doesn't care about byte order issues in unstructured data and isn't aware of them. There are no limitations on characters that may appear in unstructured data; however, the reader of such data (either a client or a server) will always know, from a preceding text line, the exact length of the data block being transmitted. Text lines are always terminated by \r\n. Unstructured data is _also_ terminated by \r\n, even though \r, \n or any other 8-bit characters may also appear inside the data. Therefore, when a client retrieves data from a server, it must use the length of the data block (which it will be provided with) to determine where the data block ends, and not the fact that \r\n follows the end of the data block, even though it does. Keys ---- Data stored by memcached is identified with the help of a key. A key is a text string which should uniquely identify the data for clients that are interested in storing and retrieving it. Currently the length limit of a key is set at 250 characters (of course, normally clients wouldn't need to use such long keys); the key must not include control characters or whitespace. Commands -------- There are three types of commands. Storage commands (there are three: "set", "add" and "replace") ask the server to store some data identified by a key. The client sends a command line, and then a data block; after that the client expects one line of response, which will indicate success or faulure. Retrieval commands (there is only one: "get") ask the server to retrieve data corresponding to a set of keys (one or more keys in one request). The client sends a command line, which includes all the requested keys; after that for each item the server finds it sends to the client one response line with information about the item, and one data block with the item's data; this continues until the server finished with the "END" response line. All other commands don't involve unstructured data. In all of them, the client sends one command line, and expects (depending on the command) either one line of response, or several lines of response ending with "END" on the last line. A command line always starts with the name of the command, followed by parameters (if any) delimited by whitespace. Command names are lower-case and are case-sensitive. Expiration times ---------------- Some commands involve a client sending some kind of expiration time (relative to an item or to an operation requested by the client) to the server. In all such cases, the actual value sent may either be Unix time (number of seconds since January 1, 1970, as a 32-bit value), or a number of seconds starting from current time. In the latter case, this number of seconds may not exceed 60*60*24*30 (number of seconds in 30 days); if the number sent by a client is larger than that, the server will consider it to be real Unix time value rather than an offset from current time. Error strings ------------- Each command sent by a client may be answered with an error string from the server. These error strings come in three types: - "ERROR\r\n" means the client sent a nonexistent command name. - "CLIENT_ERROR <error>\r\n" means some sort of client error in the input line, i.e. the input doesn't conform to the protocol in some way. <error> is a human-readable error string. - "SERVER_ERROR <error>\r\n" means some sort of server error prevents the server from carrying out the command. <error> is a human-readable error string. In cases of severe server errors, which make it impossible to continue serving the client (this shouldn't normally happen), the server will close the connection after sending the error line. This is the only case in which the server closes a connection to a client. In the descriptions of individual commands below, these error lines are not again specifically mentioned, but clients must allow for their possibility. Storage commands ---------------- First, the client sends a command line which looks like this: <command name> <key> <flags> <exptime> <bytes>\r\n - <command name> is "set", "add" or "replace" "set" means "store this data". "add" means "store this data, but only if the server *doesn't* already hold data for this key". "replace" means "store this data, but only if the server *does* already hold data for this key". - <key> is the key under which the client asks to store the data - <flags> is an arbitrary 16-bit unsigned integer (written out in decimal) that the server stores along with the data and sends back when the item is retrieved. Clients may use this as a bit field to store data-specific information; this field is opaque to the server. - <exptime> is expiration time. If it's 0, the item never expires (although it may be deleted from the cache to make place for other items). If it's non-zero (either Unix time or offset in seconds from current time), it is guaranteed that clients will not be able to retrieve this item after the expiration time arrives (measured by server time). - <bytes> is the number of bytes in the data block to follow, *not* including the delimiting \r\n. <bytes> may be zero (in which case it's followed by an empty data block). After this line, the client sends the data block: <data block>\r\n - <data block> is a chunk of arbitrary 8-bit data of length <bytes> from the previous line. After sending the command line and the data blockm the client awaits the reply, which may be: - "STORED\r\n", to indicate success. - "NOT_STORED\r\n" to indicate the data was not stored, but not because of an error. This normally means that either that the condition for an "add" or a "replace" command wasn't met, or that the item is in a delete queue (see the "delete" command below). Retrieval command: ------------------ The retrieval command looks like this: get <key>*\r\n - <key>* means one or more key strings separated by whitespace. After this command, the client expects zero or more items, each of which is received as a text line followed by a data block. After all the items have been transmitted, the server sends the string "END\r\n" to indicate the end of response. Each item sent by the server looks like this: VALUE <key> <flags> <bytes>\r\n <data block>\r\n - <key> is the key for the item being sent - <flags> is the flags value set by the storage command - <bytes> is the length of the data block to f
评论
    相关推荐
    • memcached服务器
      memcached服务器,安装包。memcached服务器,安装包。
    • iocp服务器客户端混合框架
      //连接远程服务器成功 或 接收到一个远程连接时,本函数将会被ioc.dll回调.在本函数中,应该向客户端列表中添加节点,记得加锁 // //2.s :套接字句柄,标志着一个新的连接 //3.u_addr:对端的IP地址,网络字节序 //4.u_...
    • EMC备份案例
      EMC备份软件 硬件资料 大连理工大学客户案例 2009年下半年,大连理工大学网络与信息...进一步扩大服务器虚拟化,将校园门户等关键应用迁移到虚拟化环境。这 意味着,大连理工大学在虚拟化应用方面走在同行和业界前列。
    • FreeRTOS零散:FreeRTOS的零星服务器调度程序分支
      FreeRTOS-arduino 这是Richard Barry的freeRTOS的一种形式。 它被创建为用于在arduino uno上进行的实时系统分配。 它使用具有实现的memcpy和realloc方法的heap4.c而不是heap3。 堆设置为1024字节。...
    • EMC配置手册
      EMC自从和DELL合作后,销量暴涨,那么在如今大规模使用的趋势下,作为企业的存储管理者,如何使用和配置EMC也成为了必要的常识。通过这篇文章,希望能对你深入地了解存储系统有所帮助。
    • EMC器件详解
      详细介绍EMC相关的每个器件的使用原理以及在EMC设计过程中这些器件滤掉的干扰
    • GloopBot:适用于ConU BIOBIOCHEMCHEM不和谐服务器的实用程序bot
      ConU BIO / BIOCHEM / CHEM不和谐服务器的实用程序bot。 所有命令列表 Gloop bot的所有命令均以前缀“>”表示。 > ping 返回以毫秒为单位的延迟。 >报名[部门] [班级编号] 唯一可用的部门是生物学和化学部门。 ...
    • EMC存储容灾
      企业或运营商数据存储EMC异地容灾解决方案
    • EMC存储最佳实践手册
      因此,EMC推荐你使用Navisphere Analyzer来分析你的阵列的工作情形,并且要定期的复习和回顾相关文档的基础知识。同时,请记住在配置一个阵列的时候很少有显而易见的选择,所以在有疑问的时候最好是按照默认的配置和...
    • GaussDB_100_1.0.1-DATABASE-REDHAT-64bit.tar.gz
      guassdb100在redhat上安装包,单机部署的包,安装步骤请看我的文中介绍,经过大量实验搭建总结出来的文档