On 21 October 2016 at 12:20, Guillaume Smet
wrote:
> I always prefer to migrate early to the right solution when there is a
> compelling reason to do so and a clear logic in it.
I totally agree with that, but I think it's more about what we promised to
users than about what we think is the best
On Wed, Oct 19, 2016 at 11:59 AM, Sanne Grinovero
wrote:
> On 19 October 2016 at 10:44, Yoann Rodiere wrote:
> > About backward compatibility, I guess there are two options:
> >
> >- If the last released version of the artifact used to contain only
> the
> >embedded mode, we can use mave
Splitting in 3 modules sounds good to me.
I was sure in past there was some opposition about having additional modules.
I might have imagined it
On Wed, Oct 19, 2016 at 10:59 AM, Sanne Grinovero wrote:
> On 19 October 2016 at 10:44, Yoann Rodiere wrote:
>> Is there any particular reason why we
On 19 October 2016 at 10:44, Yoann Rodiere wrote:
> Is there any particular reason why we would not want to create three
> artifacts, besides backward compatibility? It seems the obvious and ideal
> solution, but I might be missing something.
>
> If there is common code, we can always create a fou
I would prefer to see these modules split as 3 different Maven
modules, but I wouldn't personally consider such work a priority.
Splitting them up would make for "lighter" fragments for e.g. Swarm,
but at the cost of a couple more paragraphs of documentation which
needs to be understood (more comp
Is there any particular reason why we would not want to create three
artifacts, besides backward compatibility? It seems the obvious and ideal
solution, but I might be missing something.
If there is common code, we can always create a fourth -neo4j-core artifact
that would have no interest to user
The integration with Neo4j in OGM makes it possible for a user to
select the strategy that he wants to use to connect to an embedded or
remote Neo4j instance.
There are 3 possible options:
1) Embedded mode, Neo4j run in the same JVM
2) Remote via HTTP interface using RestEasy
3) Remote via the Bolt
