[
https://issues.apache.org/jira/browse/IGNITE-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321204#comment-15321204
]
Pavel Tupitsyn edited comment on IGNITE-3275 at 6/8/16 7:21 PM:
----------------------------------------------------------------
I imagine that main use case is connecting to a node from a pure .NET code via
HTTP.
If we publish REST jars in a separate NuGet package, there is no space concern.
However, I did not know that REST API in Java is nearly deprecated, where does
it say that? visorcmd uses REST, as I understand
(http://apache-ignite-users.70518.x6.nabble.com/Is-it-possible-to-disable-TcpRestProtocol-td5461.html).
was (Author: ptupitsyn):
I imagine that main use case is connecting to a node from a pure .NET code via
HTTP.
If we publish REST jars in a separate NuGet package, there is no space concern.
However, I did not know that REST API in Java is nearly deprecated, where does
it say that?
> .NET: Enable REST HTTP in .NET nodes
> ------------------------------------
>
> Key: IGNITE-3275
> URL: https://issues.apache.org/jira/browse/IGNITE-3275
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Affects Versions: 1.6
> Reporter: Pavel Tupitsyn
> Fix For: 1.7
>
>
> * Include REST HTTP jars in NuGet (either in core, or in a separate package).
> Keep in mind NuGet size limitation
> * Add required options to IgniteConfiguration to enable/disable REST
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
