19a6b34358
Change-Id: Iff9166dd7baa3d60b70ffab5ce9a692d211fa4fb BUG: 811311 Signed-off-by: Vijay Bellur <vbellur@redhat.com> Reviewed-on: http://review.gluster.org/5091 Reviewed-by: Justin Clift <jclift@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com>
19 lines
833 B
Plaintext
19 lines
833 B
Plaintext
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).
|
|
|