ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Sapego <isap...@gridgain.com>
Subject Re: Thin clients features wiki page
Date Wed, 16 May 2018 09:53:45 GMT
Fixed for .NET.

What about NodeJS? Alexey?

Best Regards,
Igor

On Wed, May 16, 2018 at 12:48 PM, Pavel Tupitsyn <ptupitsyn@apache.org>
wrote:

> Ignite.NET client is thread-safe as stated in XMLDoc [1]
>
> [1]
> https://github.com/apache/ignite/blob/master/modules/
> platforms/dotnet/Apache.Ignite.Core/Client/IIgniteClient.cs
>
> On Wed, May 16, 2018 at 12:34 PM, Guru Stron <gurustronpublic@gmail.com>
> wrote:
>
> >  Hi Igor,
> >
> > Nice one!
> >
> > On 16 May 2018 at 11:26, Igor Sapego <isapego@apache.org> wrote:
> >
> > > Pavel,
> > >
> > > This is about concurrent usage of the same connection (client)
> > > by several threads.
> > >
> > > By the ways guys, I wanted to ask you, if your clients support this
> > > feature, as I was not sure. I mean, protocol seems to be designed
> > > to support such use-case, but I was not sure about clients.
> > >
> > > Best Regards,
> > > Igor
> > >
> > > On Tue, May 15, 2018 at 10:46 PM, Pavel Tupitsyn <ptupitsyn@apache.org
> >
> > > wrote:
> > >
> > > > Hi Igor,
> > > >
> > > > Thanks for creating this!
> > > > One question: what is `Multithreading` feature?
> > > >
> > > > Pavel
> > > >
> > > > On Tue, May 15, 2018 at 9:45 PM, Denis Magda <dmagda@gridgain.com>
> > > wrote:
> > > >
> > > > > Igor,
> > > > >
> > > > > That's a valid point. Will see how it goes. As for the new
> > > documentation
> > > > > engine, there are no more arguments. We will try to migrate within
> > 2.6.
> > > > > Just need to find more contributors who would help with this.
> > > > >
> > > > > --
> > > > > Denis
> > > > >
> > > > > On Tue, May 15, 2018 at 2:11 AM, Igor Sapego <isapego@apache.org>
> > > wrote:
> > > > >
> > > > > > Thanks for proposals, guys, I will do this.
> > > > > >
> > > > > > Denis,
> > > > > > Readme.io is not very convenient for some big tables. They look
> OK,
> > > > > > while they have 3-4 columns, but if we are going to add more
> > clients
> > > > > > (or should I say "when") it is going to be a mess. This may
be a
> > one
> > > > > > more argument when we consider to change documentation engine.
> > > > > >
> > > > > >
> > > > > > Best Regards,
> > > > > > Igor
> > > > > >
> > > > > > On Tue, May 15, 2018 at 2:37 AM, Denis Magda <
> dmagda@gridgain.com>
> > > > > wrote:
> > > > > >
> > > > > >> Igor, thanks for putting together the page.
> > > > > >>
> > > > > >> As for the immediate improvements, I'm backing up Alexey's
> > > > suggestions.
> > > > > >>
> > > > > >> This page deserves to be moved to the readme.io. We'll do
that
> > once
> > > > > it's
> > > > > >> sorted out how to group the thin clients' documentation.
> > > > > >>
> > > > > >> --
> > > > > >> Denis
> > > > > >>
> > > > > >> On Mon, May 14, 2018 at 12:39 PM, Alexey Kosenchuk <
> > > > > >> alexey.kosenchuk@nobitlost.com> wrote:
> > > > > >>
> > > > > >>> Hi Igor,
> > > > > >>>
> > > > > >>> "Get Binary Cache" (if it is about getting a complex
object in
> a
> > > > > >>> "binary" form, w/o deserialization) - is supported by
NodeJS:
> > > > > >>> BinaryObject is returned for a complex object if an
app has not
> > > > > >>> specified another JavaScript Object for deserialization.
> > > > > >>>
> > > > > >>> Maybe worth to add type registration functionality:
> > > > > >>> - complex object type registration (supported by NodeJS)
> > > > > >>> - enum type registration (not supported by NodeJS)
> > > > > >>> - type name registration (not supported by NodeJS)
> > > > > >>>
> > > > > >>> Also, maybe add a list of all type codes, supported
for read
> and
> > > > write.
> > > > > >>> But not sure, as all of them are supported by all three
> clients.
> > > > > >>>
> > > > > >>> Thanks,
> > > > > >>> -Alexey
> > > > > >>>
> > > > > >>> 14.05.2018 22:06, Igor Sapego пишет:
> > > > > >>>
> > > > > >>> Hello Igniters,
> > > > > >>>>
> > > > > >>>> I've created a new page in wiki, that summarizes
a features
> > > > > >>>> availability of thin clients. It should help us
to plan
> > > development
> > > > > >>>> of thin clients while also helping out users to
understand a
> > state
> > > > > >>>> of clients.
> > > > > >>>>
> > > > > >>>> Check it out and tell me what you think. And if
there are some
> > > > > >>>> mistakes, don't hesitate telling me.
> > > > > >>>>
> > > > > >>>> [1] -
> > > > > >>>> https://cwiki.apache.org/confluence/display/IGNITE/Thin+clie
> > > > > >>>> nts+features
> > > > > >>>>
> > > > > >>>> Best Regards,
> > > > > >>>> Igor
> > > > > >>>>
> > > > > >>>>
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message