Dmitriy Setrakyan created IGNITE-128:
----------------------------------------
Summary: Ignite does need thin-client APIs as all public APIs can
be used on clients
Key: IGNITE-128
URL: https://issues.apache.org/jira/browse/IGNITE-128
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Dmitriy Setrakyan
Assignee: Vladimir Ozerov
Priority: Blocker
Fix For: sprint-1
I believe the whole "client" package can be moved to "internal" is it is only
used internally by JDBC driver. Going forward we will refactor the JDBC driver
to use standard GridGain APIs.
Note, that we still need some configuration to remain in Ignite in order to
support HTTP connectivity over Jetty or Memcached connectivity.
For that we should rename {{ClientConnectionConfiguration}} to
{{org.apache.ignite.configuration.ConnectorConfiguration}} with leave the
following properties:
- jettyPath
- restPortRange -> rename to tcpPortRange
- restAccessibleFolders should be removed together with "log" command which
needs it.
- restExecSvc -> execSvc
- restSvcShutdown -> svcShutdown (do we need it?)
- clientMsgInterceptor -> msgInterceptor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
