YUKI Hiroshi
null+****@clear*****
Fri Feb 7 15:49:30 JST 2014
YUKI Hiroshi 2014-02-07 15:49:30 +0900 (Fri, 07 Feb 2014) New Revision: 3031d36a1e3db047858d4b9e18fc0b342f4f6511 https://github.com/droonga/droonga.org/commit/3031d36a1e3db047858d4b9e18fc0b342f4f6511 Message: Make examples of plugin usecases a list Modified files: tutorial/plugin-development/index.md Modified: tutorial/plugin-development/index.md (+3 -3) =================================================================== --- tutorial/plugin-development/index.md 2014-02-07 15:40:51 +0900 (db17e3f) +++ tutorial/plugin-development/index.md 2014-02-07 15:49:30 +0900 (f06cff4) @@ -19,9 +19,9 @@ This makes droonga flexible. Generally, data processing tasks in the real world need custom treatments of the data, in various stages of the data stream. This is not easy to be done in one-size-fits-all approach. -One may want to modify input queries to work well with other systems, one may want to modify output to help other systems understand the result. -One may want to do more complex data processing than that provided by Droonga as built-in, to have direct storage access for efficiency. -One may need to control data distribution logic and collection logic of Droonga to profit from distributed nature of Droonga. + * One may want to modify incoming requests to work well with other systems, one may want to modify outgoing responses to help other systems understand the result. + * One may want to do more complex data processing than that provided by Droonga as built-in, to have direct storage access for efficiency. + * One may need to control data distribution and collection logic of Droonga to profit from distributed nature of Droonga. You can use plugins in those situations. -------------- next part -------------- HTML����������������������������...Download