You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geode.apache.org by Luke Shannon <ls...@pivotal.io> on 2015/06/28 18:47:15 UTC
Client and Server Dependancies
I have been playing with developing applications using Spring Boot that
work with Geode in a client server model.
This is very helpful:
https://spring.io/blog/2015/06/12/spring-data-gemfire-supports-apache-geode
But I wonder if it would make sense to have a set of dependancies for
client projects and another for a server side project?
If I just want to code a client, would I need all of the dependancies that
come with the entire Geode package?
I am bringing this up because it seems like I am having some dependancy
issues when I bring the Geode dependancy into an existing Boot app. I have
not figured it out yet, so this could be user error, but I wonder if things
like gemfire-jgroups are needed for a client application?
Join the Toronto Pivotal Usergroup:
http://www.meetup.com/Toronto-Pivotal-User-Group/
Re: Client and Server Dependancies
Posted by Bruce Schuchardt <bs...@pivotal.io>.
I think the JGroups jar is needed for clients. All of the
DistributedMember address objects in Geode refer to the JGroups
IpAddress class, and clients have these.
Le 6/29/2015 9:27 AM, Darrel Schneider a écrit :
> Usually a client will not need jgroups since it should not have any
> peers so I think you are correct that the client dependencies could be
> less than the server dependencies. Seems like a good idea.
>
>
>
> On Sun, Jun 28, 2015 at 9:47 AM, Luke Shannon <lshannon@pivotal.io
> <ma...@pivotal.io>> wrote:
>
> I have been playing with developing applications using Spring Boot
> that work with Geode in a client server model.
>
> This is very helpful:
> https://spring.io/blog/2015/06/12/spring-data-gemfire-supports-apache-geode
>
> But I wonder if it would make sense to have a set of dependancies
> for client projects and another for a server side project?
>
> If I just want to code a client, would I need all of the
> dependancies that come with the entire Geode package?
>
> I am bringing this up because it seems like I am having some
> dependancy issues when I bring the Geode dependancy into an
> existing Boot app. I have not figured it out yet, so this could be
> user error, but I wonder if things like gemfire-jgroups are needed
> for a client application?
>
>
>
>
>
>
>
>
>
> Join the Toronto Pivotal Usergroup:
> http://www.meetup.com/Toronto-Pivotal-User-Group/
>
>
Re: Client and Server Dependancies
Posted by Darrel Schneider <ds...@pivotal.io>.
Usually a client will not need jgroups since it should not have any peers
so I think you are correct that the client dependencies could be less than
the server dependencies. Seems like a good idea.
On Sun, Jun 28, 2015 at 9:47 AM, Luke Shannon <ls...@pivotal.io> wrote:
> I have been playing with developing applications using Spring Boot that
> work with Geode in a client server model.
>
> This is very helpful:
> https://spring.io/blog/2015/06/12/spring-data-gemfire-supports-apache-geode
>
> But I wonder if it would make sense to have a set of dependancies for
> client projects and another for a server side project?
>
> If I just want to code a client, would I need all of the dependancies that
> come with the entire Geode package?
>
> I am bringing this up because it seems like I am having some dependancy
> issues when I bring the Geode dependancy into an existing Boot app. I have
> not figured it out yet, so this could be user error, but I wonder if things
> like gemfire-jgroups are needed for a client application?
>
>
>
>
>
>
>
>
>
> Join the Toronto Pivotal Usergroup:
> http://www.meetup.com/Toronto-Pivotal-User-Group/
>