Alright, let's see if anybody steps in. Anyway, feel free to create tickets in our JIRA using "spring" as a label. If we fail to persuade the Spring folks then it's fine to host the integration in our extensions repository.
- Denis On Mon, Jun 15, 2020 at 1:55 PM Данилов Семён <samvi...@yandex.ru> wrote: > Hello Denis, > > We need people whose opinion is valued in the Spring community, yes, > because so far Spring Project members rejected the idea of adding Ignite > dependency. > > - > Semyon > > 15.06.2020, 21:40, "Denis Magda" <dma...@apache.org>: > > Hello Semyon, > > > > That's a very reasonable suggestion. Whom do you mean under the Spring > > Project committers - those who already contribute to the Spring > > ecosystem and have some merit there, or those among us who are willing to > > contribute the integration? > > > > - > > Denis > > > > On Mon, Jun 15, 2020 at 6:27 AM Данилов Семён <samvi...@yandex.ru> > wrote: > > > >> Hello Igniters! > >> > >> I recently stumbled upon a fact that Apache Ignite doesn't have any > Spring > >> integrations in spring-project repositories. > >> To increase Ignite's popularity, I think it would be best to fix that > >> inconvenience. The best way to start would be to create > >> a web-session repository based on Ignite cache. For this task we need > >> Spring Project committers who can support the idea > >> of creating separate module for Ignite in Spring Session repository. > The > >> main objection of Spring Community members is > >> that Spring Session project already provides MapSession which can be > >> backed by Apache Ignite map. But I think that this > >> solution is very limited, because we have zero control on flushing > policy. > >> Also, we must keep track if changes have been > >> made since last save and we should persist session to cache again. > >> > >> Kind regards, > >> Semyon. >
