From ee267bc31d70d66d40e78b064044d1a39d3d8360 Mon Sep 17 00:00:00 2001 From: tripathyr Date: Tue, 23 Jun 2020 19:32:49 +0530 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9917673..a5ba027 100644 --- a/README.md +++ b/README.md @@ -612,5 +612,5 @@ Application data system is a legacy data field without vector clock support in o However, since Application Data system has no vector clock support in SEND and REQUEST OPTIONS, it will always give the entire data set stored in the cloud since start, and user will have to custom handle the output of it himself. Our client side framework will not stoe it for the user. -Usually ObjectData and GeneralData systems will support most of user needs. But for cases when the user wants the entire cloud data set, and no client side framework handling, he should use ApplicationData +Usually ObjectData and GeneralData systems will support most of user needs. But for cases when the user wants the entire cloud data set, and no client side framework handling, he should use ApplicationData. Although Application Data system supports lower vectorClock as a REQUEST option. If lower vectorClock is specified, it will give all cloud stored application data after that vectorClock.