Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CAGt6o8=uwTSSVR4LRpBCx+2BNOT-btX2QKjnz81p_cOZz=eTZA@mail.gmail.com>
References: <CABuYRcrnexFpu36d4j3w3gDpX9fHYo7sykNdmbTE4RTMhNLZcQ@mail.gmail.com>
 <CAGt6o8=uwTSSVR4LRpBCx+2BNOT-btX2QKjnz81p_cOZz=eTZA@mail.gmail.com>
From: Valentin Kulichenko <valentin.kulichenko@gmail.com>
Date: Mon, 7 Aug 2017 13:17:42 -0700
Message-ID: <CABuYRcq=L6LVvq2ELDdCXO04dptRSmJNeWVg+Xv1u7XrJQUhwQ@mail.gmail.com>
Subject: Re: igniterouter.sh
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="94eb2c194a06da5b3505562f8bbd"
archived-at: Mon, 07 Aug 2017 20:18:21 -0000

--94eb2c194a06da5b3505562f8bbd
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I'm pretty sure current router will not be able to work with new client
anyway, which will make even more confusing than now. I think it's better
to remove these scripts in next release (unless both client and router are
back in this release of course :) ).

-Val

On Mon, Aug 7, 2017 at 1:13 PM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> Val,
>
> Thin client is like Arnold - he'll be back ) We already working on it. I
> propose to delay this question a bit, until we understand that router is
> not needed for new thin client.
>
> =D0=BF=D0=BD, 7 =D0=B0=D0=B2=D0=B3. 2017 =D0=B3. =D0=B2 23:07, Valentin K=
ulichenko <
> valentin.kulichenko@gmail.com>:
>
> > Folks,
> >
> > Our bin folder still contains igniterouter.{sh|bat} script. Previously =
it
> > was used to support indirect access from thin client to cluster. Since
> thin
> > client is deprecated for a while, is there a use case when router can b=
e
> > used?
> >
> > I think it makes sense to remove these scripts for now. If we ever
> > resurrect this functionality, we can always bring them back.
> >
> > Thoughts?
> >
> > -Val
> >
>

--94eb2c194a06da5b3505562f8bbd--