Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
From: Andrey Kornev <andrewkornev@hotmail.com>
To: Pavel Tupitsyn <ptupitsyn@apache.org>, "dev@ignite.apache.org"
	<dev@ignite.apache.org>
Subject: Re: Thin Client Protocol documentation
Thread-Topic: Thin Client Protocol documentation
Thread-Index: AQHTY5JrNWf7hyO5MkGsF/eJfgcwTqMsrGcAgAAClQCAAarUgIAANTEAgAH9x2CAAWLVgIABzMeF
Date: Mon, 4 Dec 2017 21:06:21 +0000
Message-ID: <MWHPR2201MB1551C8BF94B46AC1080FB115CF3C0@MWHPR2201MB1551.namprd22.prod.outlook.com>
References: <CAK2_iMOi3=RVszTTeS_=-VG1tpvwB7pozD1AGOSrtrqD+-kybg@mail.gmail.com>
 <5a1fc8da.10372e0a.dfa50.4edb@mx.google.com>
 <CAK2_iMOWztTM3=rKoL0RZSGWUBc-ugogFw+weU_8A528_+LJbg@mail.gmail.com>
 <5a213111.94a7190a.ba8a3.75d9@mx.google.com>
 <CAK2_iMMdyCp8o29y4HC7ZNTG0jo6s203tcM1GQOg2nHEZsYipA@mail.gmail.com>
 <MWHPR2201MB155129ED049EE2B0AE062326CF3E0@MWHPR2201MB1551.namprd22.prod.outlook.com>,<CAK2_iMM+GoOb=iv7+2QoRiioXghiw9JfKK-FEsbV3OFnpWHrTQ@mail.gmail.com>
In-Reply-To: <CAK2_iMM+GoOb=iv7+2QoRiioXghiw9JfKK-FEsbV3OFnpWHrTQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [C3wnOPaDVv0+mdfP6NfQ71k6fD5GRU3ZriSk2kF4MHp9zkMbZV6lKEM4Jmn9STId]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1;BY2NAM03HT194;6:+7kEamlUzLG04XgVLchvoa2x+9BGI6PxxImL2fdjC8af32Q1vUoFU60MYgQJhkZ3DaavCTQaR+QEufX2QvZFPoxVnrfHgmwIS6oSG7Z+9ScdGbnipeEcwGEnhRgwrEmPXMinp478zfr7uTbmB8ONNFF93cVsQai/mmRQtUf09qaLp9sdBfkjkuySkR8/+a2N/DW0Rev0HuYLbI+0sxGqtjlVrRerMo4tZwnxM7SAYekY5QmDn3nAyYLnXdKlsXS5ZYuRhXg/CxnWDxYF69trWPF0sBuxkdoAoyBu0wVkh5Ff/ONzNHWU2wgqUU5PMoK85XcxSMlI7gyiFepO/Ot9LmYUa7P71D5PP8W6MmXuBUE=;5:WFrjutpryUocyxa8dv6qf7R6z+CmltwhjrLXDZFeopf5X7ugVp+Yf5oP176KS5zj5ZF8NoNgUC7WAYO9bKe61MlSWtEkjjp2/TCijbfZxBUC4+MVq3MdMiq3dqrVN8riv3e2a915187v0qFUb4dInvrh9UuvdO3jkT3gkUaL7EU=;24:Mu2wsZ8k1zytY/VGC57gxGBSVCpNeRHJEt3unHjdc+dSI4RWCxD7lPRtdyejdskSAo09ymGixAlfuqUoBqthpOF/B2VdbBGMRbyHpJlz/dY=;7:2mZUQepS89RxPKsH0RMPOx0vecsZdKNrVTRalCIrLIM4mxZXNNraxtxvWTTJeHLSNoO8YXXE9WwvuKAEDBNRk9gNEEfXzyQvuMVzptwu/Nwy2zJwBbllGKAPh9HSyi9ZfZ0uIY9BdvwalYNTgBCAoyQXmAPAY3qyqvk0E46yFyoyQQkjCCIi9d4qBfWJj1vD8P2k3X3eTywTvQaq6GF9yEKHv+q5wlzcPk/bOtljD9//5hRnoPhnfMiXSRnpL7fc
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045);SRVR:BY2NAM03HT194;
x-ms-traffictypediagnostic: BY2NAM03HT194:
x-ms-office365-filtering-correlation-id: 33ad1fa7-1876-4fc6-fded-08d53b5adf05
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(444000031);SRVR:BY2NAM03HT194;BCL:0;PCL:0;RULEID:(100000803101)(100110400095);SRVR:BY2NAM03HT194;
x-forefront-prvs: 051158ECBB
x-forefront-antispam-report: SFV:NSPM;SFS:(7070007)(98901004);DIR:OUT;SFP:1901;SCL:1;SRVR:BY2NAM03HT194;H:MWHPR2201MB1551.namprd22.prod.outlook.com;FPR:;SPF:None;LANG:;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_MWHPR2201MB1551C8BF94B46AC1080FB115CF3C0MWHPR2201MB1551_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 33ad1fa7-1876-4fc6-fded-08d53b5adf05
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Dec 2017 21:06:21.6194
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2NAM03HT194
archived-at: Mon, 04 Dec 2017 21:06:33 -0000

--_000_MWHPR2201MB1551C8BF94B46AC1080FB115CF3C0MWHPR2201MB1551_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Pavel,

Thanks! While we're at it, are there any plans to add cluster-related opera=
tions? For example, I think it'd be nice to allow the thin clients to obtai=
n a current topology snapshot. This would make it possible the clients to s=
end requests directly to the affinity host for colocated computation. To ma=
ke it even more useful, all server responses could optionally include the t=
opology version the operation has been executed against. This would effecti=
vely give us a kind out-of-band topology change notification mechanism. Thi=
s way the clients can detect a topology change and refresh the topology sna=
pshot next time they need to compute affinity.

Regards
Andrey
________________________________
From: Pavel Tupitsyn <ptupitsyn@apache.org>
Sent: Sunday, December 3, 2017 9:23 AM
To: dev@ignite.apache.org
Subject: Re: Thin Client Protocol documentation

Hi Andrey,

Compute and other APIs are certainly planned, cache is just a start.
We intentionally limit the scope to actually release something in 2.4 and
not delay it further.

Adding operations to existing protocol is relatively easy.
Current focus is to make sure that the protocol itself is solid and
future-proof.

Thanks,
Pavel

--_000_MWHPR2201MB1551C8BF94B46AC1080FB115CF3C0MWHPR2201MB1551_--