Vladimir,
I disagree. We already have client mode which support the full Ignite API.
Here we are talking about the new client binary protocol. To my knowledge,
the following APIs can be implemented over the new binary protocol:
- JDBC
- ODBC
- REST
- .NET Thin
All these protocols are already cu
+1 one for the first approach. The users will start with a documentation page
where we can define in a table format the scope of supported APIs.
—
Denis
> On Sep 12, 2017, at 3:06 AM, Pavel Tupitsyn wrote:
>
> I prefer the first approach.
> Users can easily switch to client mode, run their cod
I prefer the first approach.
Users can easily switch to client mode, run their code and see what works
and what not.
Second approach may require huge amount of refactoring to even try the
client mode.
And new users have to make a tough choice, because switching later is hard.
As a middle ground
Igniters,
We are developing new thin client. There are two approaches on how to
design it's interfaces - either re-use existing Ignite interfaces, or
define new. Both approaches has pros and cons
*1) Re-use interfaces*
This approach is used in Hazelcast. Both server and client share the same
API
