4bfc868fa3
compatible / memcached, and has more features(as follows): * persistent storage (you can use flare as persistent memcached) * pluggable storage (currently only Tokyo Cabinet is available, though:) * data replication (synchronous or asynchronous) * data partitioning (automatically partitioned according to # of master servers (clients do not have to care about it)) * dynamic reconstruction, and partitioning (you can dynamically (I mean, without any service interruption) add slave servers and partition master servers) * node monitoring and failover (if any server is down, the server is automatically isolated from active servers and another slave server is promoted to master server) * request proxy (you can always get same result regardless of servers you connect to. so you can think flare servers as one big key-value storage) * over 256 bytes keys, and over 1M bytes values are available WWW: http://labs.gree.jp/Top/OpenSource/Flare-en.html
18 lines
654 B
C
18 lines
654 B
C
--- src/flared/ini_option.h.orig 2009-10-09 19:08:47.000000000 +0900
|
|
+++ src/flared/ini_option.h 2010-05-30 00:33:49.304567301 +0900
|
|
@@ -26,6 +26,7 @@
|
|
|
|
int _back_log;
|
|
string _config_path;
|
|
+ string _pid_path;
|
|
bool _daemonize;
|
|
string _data_dir;
|
|
string _index_server_name;
|
|
@@ -84,6 +85,7 @@
|
|
|
|
int get_back_log() { return this->_back_log; };
|
|
string get_config_path() { return this->_config_path; };
|
|
+ string get_pid_path() { return this->_pid_path; };
|
|
bool is_daemonize() { return this->_daemonize; };
|
|
string get_data_dir() { return this->_data_dir; };
|
|
string get_index_server_name() { return this->_index_server_name; };
|