|author||Amar Tumballi <firstname.lastname@example.org>||2010-06-21 07:00:04 +0000|
|committer||Anand V. Avati <email@example.com>||2010-06-21 20:21:10 -0700|
Signed-off-by: Amar Tumballi <firstname.lastname@example.org> Signed-off-by: Raghavendra G <email@example.com> Signed-off-by: Anand V. Avati <firstname.lastname@example.org> BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875
Diffstat (limited to 'doc/rpc-for-glusterfs.changes-done.txt')
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/rpc-for-glusterfs.changes-done.txt b/doc/rpc-for-glusterfs.changes-done.txt
new file mode 100644
@@ -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).