YUKI Hiroshi
null+****@clear*****
Wed Feb 5 18:20:21 JST 2014
YUKI Hiroshi 2014-02-05 18:20:21 +0900 (Wed, 05 Feb 2014) New Revision: 1e6dcc547288a967cd134b8c10e4548edea99b88 https://github.com/droonga/droonga.org/commit/1e6dcc547288a967cd134b8c10e4548edea99b88 Message: Fix version: 1.0 => 1.0.0 Modified files: _posts/2014-02-09-release.md Modified: _posts/2014-02-09-release.md (+5 -5) =================================================================== --- _posts/2014-02-09-release.md 2014-02-05 18:19:11 +0900 (0a0a80f) +++ _posts/2014-02-09-release.md 2014-02-05 18:20:21 +0900 (c0c17e4) @@ -20,21 +20,21 @@ The release has the following improvements: * Now you can develop any Droonga plugin which translates request and response messages, between the Droonga Engine and the client including the Protocol Adapter. See the [plugin development tutorial](/tutorial/plugin-development/) for more details. * Other type plugins will become developpable in near future, so please wait for the next release... -## Why we ship Droonga 0.9.9 before 1.0? +## Why we ship Droonga 0.9.9 before 1.0.0? -On the [previous release](/news/2014/01/29/release), we announced that we'll release the version 1.0 today. However, now the version 0.9.9 is released. Why not 1.0? There are two reasons mainly. +On the [previous release](/news/2014/01/29/release), we announced that we'll release the version 1.0.0 today. However, now the version 0.9.9 is released. Why not 1.0.0? There are two reasons mainly. -First, plugin APIs were not matured yet. While we were brushing up internal operations of Droonga, we realized that it is hard to develop plugins, because current implementations were built on disorganized codes. Moreover, if people develop any plugin based on the current bad APIs and publish them, then they will become obsolete in very near future, because we define new plugin APIs which completely incompatible with the old one, on the version 1.1, 1.2, or 1.3. We thought that we should stabilize plugin APIs before the version 1.0 become public. +First, plugin APIs were not matured yet. While we were brushing up internal operations of Droonga, we realized that it is hard to develop plugins, because current implementations were built on disorganized codes. Moreover, if people develop any plugin based on the current bad APIs and publish them, then they will become obsolete in very near future, because we define new plugin APIs which completely incompatible with the old one, on the version 1.1, 1.2, or 1.3. We thought that we should stabilize plugin APIs before the version 1.0.0 become public. Second, we had to rethink the message flow around distributed operations. Droonga should support recursive distributions of messages, but the current message flow couldn't describe such complex combinations of messages. To introduce such flexibility to Droonga, we had to reconstruct plugin APIs around distributing and collection phases. But rewriting of those mechanism takes much more time and we couldn't complete it before today. -Then, we decided to postpone shipping of the version 1.0. +Then, we decided to postpone shipping of the version 1.0.0. Instead, we've stabilized plugin APIs around InputAdapter and OutputAdapter ahead of other type plugins. Now you can study how to develop Droonga plugins, via steps to develop InputAdapter and/or OutAdapter type plugins. ## Conclusion - * Droonga 1.0.0 has been released! + * Droonga 0.9.9 has been released! * Now you can develop plugins which translate request and response messages between the Droonga Engine and the client (including the Protocol Adapter). See the [plugin development tutorial](/tutorial/plugin-development/). * Other type plugins will become developable in the next release. * Droonga project will release a new version every month! -------------- next part -------------- HTML����������������������������...ダウンロード
