From 19a6b34358cb2b12aec0eba1659fca65a50aa3a3 Mon Sep 17 00:00:00 2001 From: Vijay Bellur Date: Sun, 26 May 2013 13:37:50 +0530 Subject: doc: Move relevant files out of legacy. Change-Id: Iff9166dd7baa3d60b70ffab5ce9a692d211fa4fb BUG: 811311 Signed-off-by: Vijay Bellur Reviewed-on: http://review.gluster.org/5091 Reviewed-by: Justin Clift Tested-by: Gluster Build System --- doc/rpc-for-glusterfs.changes-done.txt | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/rpc-for-glusterfs.changes-done.txt (limited to 'doc/rpc-for-glusterfs.changes-done.txt') diff --git a/doc/rpc-for-glusterfs.changes-done.txt b/doc/rpc-for-glusterfs.changes-done.txt new file mode 100644 index 000000000..6bbbca788 --- /dev/null +++ b/doc/rpc-for-glusterfs.changes-done.txt @@ -0,0 +1,18 @@ +This document serves as a basic coding standard/practise for further +developments after proper protocol layer is implemented. + +With this release we are bringing abstraction based on xlator driven +operation and protocol driven operation. ie, all the client side (fuse) +operations are xlator driven operations and will come with 'op' value +taken from 'libglusterfs/'. + +All the server protocol driven operations are driven by which ever +version of protocol is used. + +All the currently implemented fops will remain, and 'getspec' being generated +by top level and passes through translator graph, is treated as an 'fop'. + +All new 'gluster' and 'glusterd' related calls will be _mgmt_ calls instead of +fops. All release, releasedir and forget are treated as fops (but they won't +come with requirement to use STACK_WIND and STACK_UNWIND). + -- cgit