Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1460502224142-4103.post@n6.nabble.com>
References: 
 <CADheoBmZZEKLBMhTvfXM6n34fzpjsSKFwi2J-rKvP8Zb0ozLPg@mail.gmail.com>
	<1460502224142-4103.post@n6.nabble.com>
Date: Wed, 13 Apr 2016 07:35:56 +0530
Message-ID: 
 <CADheoBmsYheV-Swutjh3psuZxpBskDUG7Fuh--1bq0Qgoh9niQ@mail.gmail.com>
Subject: Re: Ignite Services: How to preserve value of Local variables ?
From: Kamal C <kamaltarget@gmail.com>
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a11c29c9ee4186a053054378e

--001a11c29c9ee4186a053054378e
Content-Type: text/plain; charset=UTF-8

Thanks for your response Val.

Is service grid can be seen as a replacement for RMI?

My existing legacy code provides RMI support for the external
system to access it. I have a requirement to distribute the
application by running it in more than one node. I'm looking for
a way to provide the API Services.

Is Service grid fits for this purpose ?

--Kamal


On 13-Apr-2016 4:47 AM, "vkulichenko" <valentin.kulichenko@gmail.com> wrote:
>
> Hi Kamal,
>
> Service instance can be serialized during deployment on other nodes. In
> general it's better to make services stateless. If state is required, use
> IgniteCache instead.
>
> But your particular case you can simply make this field static. Since it
> gets the value from a system property, it will properly initialized in
each
> VM and will not be serialized.
>
> -Val
>
>
>
> --
> View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Services-How-to-preserve-value-of-Local-variables-tp4094p4103.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

--001a11c29c9ee4186a053054378e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for your response Val.<br><br>Is service grid can b=
e seen as a replacement for RMI?<br><br>My existing legacy code provides RM=
I support for the external=C2=A0<div>system=C2=A0to access it. I have a req=
uirement to distribute the=C2=A0</div><div>application by running it in mor=
e than one node. I&#39;m looking for=C2=A0</div><div>a way to provide the A=
PI Services.=C2=A0</div><div><br></div><div>Is Service grid fits for this p=
urpose ?</div><div><br></div><div>--Kamal</div><div><div><br><br><br><br>On=
 13-Apr-2016 4:47 AM, &quot;vkulichenko&quot; &lt;<a href=3D"mailto:valenti=
n.kulichenko@gmail.com">valentin.kulichenko@gmail.com</a>&gt; wrote:<br>&gt=
;<br>&gt; Hi Kamal,<br>&gt;<br>&gt; Service instance can be serialized duri=
ng deployment on other nodes. In<br>&gt; general it&#39;s better to make se=
rvices stateless. If state is required, use<br>&gt; IgniteCache instead.<br=
>&gt;<br>&gt; But your particular case you can simply make this field stati=
c. Since it<br>&gt; gets the value from a system property, it will properly=
 initialized in each<br>&gt; VM and will not be serialized.<br>&gt;<br>&gt;=
 -Val<br>&gt;<br>&gt;<br>&gt;<br>&gt; --<br>&gt; View this message in conte=
xt: <a href=3D"http://apache-ignite-users.70518.x6.nabble.com/Ignite-Servic=
es-How-to-preserve-value-of-Local-variables-tp4094p4103.html">http://apache=
-ignite-users.70518.x6.nabble.com/Ignite-Services-How-to-preserve-value-of-=
Local-variables-tp4094p4103.html</a><br>&gt; Sent from the Apache Ignite Us=
ers mailing list archive at Nabble.com.</div></div></div>

--001a11c29c9ee4186a053054378e--