support of compute functions by thin clients
I'm ok if it does not break the idea to restrict execution for the signed
code only.
On Wed, Apr 4, 2018 at 1:05 PM, Ilya Kasnacheev
wrote:
> Hello!
>
> > checksum of uploaded java code
>
> I argue not for Java code but for javascri
I'm ok if it does not break the idea to restrict execution for the signed
code only.
On Wed, Apr 4, 2018 at 1:05 PM, Ilya Kasnacheev
wrote:
> Hello!
>
> > checksum of uploaded java code
>
> I argue not for Java code but for javascript/nashorn. Ruby or PHP guys
> won't be happy about writing java
Hello!
> checksum of uploaded java code
I argue not for Java code but for javascript/nashorn. Ruby or PHP guys
won't be happy about writing java, but they can easily do JS.
(If we wanted Java, we could make it service grid-oriented. Which is an
interesting idea btw. We can frame local computatio
Hi
We can introduce the rules to use compute tasks execution:
1. Disable by default that feature (enabling will require change a
configuration property and restart cluster)
2. Disable by default code sending in the cluster (enabling will require
change a configuration property and restart clus
On Tue, Apr 3, 2018 at 5:48 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Dmitry,
>
> I just think that it's natural to have this functionality and that it would
> drastically increase flexibility of thin client. Multiple requests from
> users (one of them in this thread) seem
> >>> > > >
> >>> > > > > Hi Denis,
> >>> > > > >
> >>> > > > > We are using Ignite.Net and are planning to use 2.4 + .Net
> >Core +
> >>> > thin
> >>> > > > > c
> >
> >>> > > > > Hi Denis,
> >>> > > > >
> >>> > > > > We are using Ignite.Net and are planning to use 2.4 + .Net
> >Core +
> >>> > thin
> >>> > > > > client support to enable
o enable lightweight containerisable
>services that
>>> > > > interact
>>> > > > > with the main Ignite compute grid.
>>> > > > >
>>> > > > > These work flows are less about Get/Put style semantics, and
>more
t; > > > with the main Ignite compute grid.
>> > > > >
>> > > > > These work flows are less about Get/Put style semantics, and more
>> > about
>> > > > > using grid compute.
>> > > > >
>> > > > > Eg: Here&
ote context
> to
> > > > > render
> > > > > a bitmap tile in an ICompute:
> > > > >
> > > > > public Bitmap Execute(TileRenderRequestArgument arg)
> > > > > {
> > > > > ICompute
{
> > > > IComputeFunc func =
> new
> > > > TileRenderRequestComputeFunc();
> > > >
> > > > return
> > > > _ignite.GetCluster().ForRemotes().GetCompute().Apply(func, arg);
> > > > }
> >
tile in an ICompute:
> > > >
> > > > public Bitmap Execute(TileRenderRequestArgument arg)
> > > > {
> > > > IComputeFunc func =
> new
> > > > TileRenderRequestComputeFunc();
> > > >
> > >
r().ForRemotes().GetCompute().Apply(func, arg);
> > > }
> > >
> > > In this example, the calling context here could be a lightweight
> Kestrel
> > > web
> > > service end point delegating rendering to a remote service.
> > >
> &
-
From: Denis Magda [mailto:dma...@apache.org]
Sent: Thursday, March 15, 2018 9:32 AM
To: dev@ignite.apache.org
Subject: Re: Timeline for support of compute functions by thin clients
Raymond,
Then I would suggest you keep using the regular .NET client that supports
and optimized for
> TileRenderRequestComputeFunc();
>> >
>> > return
>> > _ignite.GetCluster().ForRemotes().GetCompute().Apply(func, arg);
>> > }
>> >
>> > In this example, the calling context here could be a lightweight Kestrel
>> >
> > }
> >
> > In this example, the calling context here could be a lightweight Kestrel
> > web
> > service end point delegating rendering to a remote service.
> >
> > Thanks,
> > Raymond.
> >
> > -Original Message-
> > From:
ge-
> From: Denis Magda [mailto:dma...@apache.org]
> Sent: Thursday, March 15, 2018 8:31 AM
> To: dev@ignite.apache.org
> Subject: Re: Timeline for support of compute functions by thin clients
>
> Hi Raymond,
>
> There are no any plans for that level of support. The
31 AM
To: dev@ignite.apache.org
Subject: Re: Timeline for support of compute functions by thin clients
Hi Raymond,
There are no any plans for that level of support. The thin clients are
targeted for classic client-server processing use cases when a client
request data from a server, does something
Hi Raymond,
There are no any plans for that level of support. The thin clients are
targeted for classic client-server processing use cases when a client
request data from a server, does something with it locally and potentially
writes changes back to the server. ICache, SQL fall under this categor
19 matches
Mail list logo
