"login force" => "login form".

On Tue, Sep 8, 2015 at 11:28 AM, Vladimir Ozerov <voze...@gridgain.com>
wrote:

> Usability concern - why do we force user doing click on "Configure now"?
> IMHO it is better to inline login force directly on the page.
>
> On Tue, Sep 8, 2015 at 11:12 AM, Alexey Kuznetsov <akuznet...@gridgain.com
> > wrote:
>
>> My question is about this feature name: "Ignite Web Console" or "Ignite
>> Web
>> Control Center"?
>>
>> On Tue, Sep 8, 2015 at 2:02 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
>> wrote:
>>
>> > Igniters,
>> >
>> > Looks like the web console feature is becoming production ready:
>> > http://104.197.2.239/
>> >
>> > In my opinion, the ability to configure Ignite and run SQL queries on
>> > Ignite clusters from a web console is a huge productivity boost and we
>> > should try to get as many community members and users to start playing
>> with
>> > it. I would like to have a link on the website to make it as accessible
>> as
>> > possible. This creates a few questions.
>> >
>> > *1. Hosting*
>> > So far the server we have been using for the development of the
>> web-console
>> > functionality was sponsored by GridGain and hosted on the GCE cloud. I
>> > think it makes sense to ask GridGain if it is possible to continue
>> hosting
>> > it once we make it available to our users as well.
>> >
>> > *2. Ignite website*
>> > Different vendors may wish to provide hosting for the Ignite
>> web-console,
>> > and potentially may wish to add their own extra features there to
>> > differentiate themselves. In the interest of neutrality, we should have
>> a
>> > page on the website listing all the vendors hosting the web-console
>> with a
>> > small blurb next to it. Something similar to Apache Subversion, for
>> > example: https://subversion.apache.org/packages.html
>> >
>> > Does anyone have any concerns with this approach?
>> >
>> > D.
>> >
>>
>>
>>
>> --
>> Alexey Kuznetsov
>> GridGain Systems
>> www.gridgain.com
>>
>
>

Reply via email to