YUKI Hiroshi
null+****@clear*****
Fri Nov 7 17:57:49 JST 2014
YUKI Hiroshi 2014-11-07 17:57:49 +0900 (Fri, 07 Nov 2014) New Revision: dd2d3a4a8c9029565da93075c98a5be489299d03 https://github.com/droonga/droonga.org/commit/dd2d3a4a8c9029565da93075c98a5be489299d03 Message: Describe improvements of Droonga 1.0.8 Modified files: news/_posts/2014-11-29-release.md Modified: news/_posts/2014-11-29-release.md (+7 -2) =================================================================== --- news/_posts/2014-11-29-release.md 2014-11-07 17:31:37 +0900 (77fc42c) +++ news/_posts/2014-11-29-release.md 2014-11-07 17:57:49 +0900 (9021cd6) @@ -12,9 +12,14 @@ A Droonga cluster works like an HTTP server compatible to [Groonga][groonga] wit Are you interested in Droonga: how it works and how useful? Let's try the [tutorial][] for an introduction, and see the [overview][] to understand Droonga's design strategy more and more. -## (summary of this release) +## Orchestration of front-end HTTP server nodes, better compatibility to Groonga, and more! + +This release Droonga 1.0.8 contains many improvements. + +Now, a front-end HTTP server node (protocol adapter, aka `droonga-http-server`) works as a member of the Droonga cluster truly. +Even if one of `droonga-engine` node become unavailable, HTTP servers automatically keep working with active `droonga-engine` nodes. +Moreover, An HTTP server automatically distributes requests from clients to multiple `droonga-engine` nodes. In other words, now it works like a load balancer. -The most important topic on this release Droonga 1.0.8 is the *(something)*. (TBD) -------------- next part -------------- HTML����������������������������...Download