Re: [infinispan-dev] Infinispan URL format

Hi Tristan! Multi tenancy is more an endpoint thing. If you look into the Configuration part of the design [1] you might notice that I'm actually routing between "hotrod-connector"s (which means between ProtocolServer instances). So to be consistent I believe the [/cachemanager] part should be

Re: [infinispan-dev] Infinispan URL format

On Wed 2016-06-01 9:31, Scott Marlow wrote: > > The [cachemanager] part is for multi-tenant servers (Hot Rod doesn't > > currently support this, so this is forward-looking). > > Obviously we will support all of the HotRod properties for specifying > > things like security, etc. > > Once you are

Re: [infinispan-dev] Infinispan URL format

On 05/30/2016 03:46 AM, Tristan Tarrant wrote: > In the past there has been talk of representing a connection to > Infinispan using a URL, in particular for HotRod. > The Hibernate OGM team is now working on adding NoSQL datasources to > WildFly, and they've asked for they should represent

Re: [infinispan-dev] Infinispan URL format

+1, a URL that gives you a different CacheManager every time you use it doesn't seem very useful. JCache also requires the the CacheManager returned for one URL to be more or less constant: * Multiple calls to this method with the same {@link URI} and * {@link ClassLoader} must return the

Re: [infinispan-dev] Infinispan URL format

The implementation proposals seem slick, but I'd have some doubts about allowing overrides to the datastore settings at this level. The hot-rod proposal looks fine, as similarly to a RDBMs it helps to figure how to connect to a specific database by expressing: - how to reach the DB - WHICH

Re: [infinispan-dev] Infinispan URL format

So you've been putting that XSL/Xpath knowledge to good use I see. I like it. Tristan On 01/06/2016 09:02, Radim Vansa wrote: > On 05/31/2016 01:33 PM, Galder Zamarreño wrote: >> Comments inline: >> >> -- >> Galder Zamarreño >> Infinispan, Red Hat >> >>> On 30 May 2016, at 09:46, Tristan

Re: [infinispan-dev] Infinispan URL format

On 05/31/2016 01:33 PM, Galder Zamarreño wrote: > Comments inline: > > -- > Galder Zamarreño > Infinispan, Red Hat > >> On 30 May 2016, at 09:46, Tristan Tarrant wrote: >> >> In the past there has been talk of representing a connection to >> Infinispan using a URL, in

Re: [infinispan-dev] Infinispan URL format

This also fits nicely with the JCache API, where a CacheProvider is expected to express a connection to a CacheManager as a URI. On Mon, May 30, 2016 at 3:46 AM, Tristan Tarrant wrote: > In the past there has been talk of representing a connection to > Infinispan using a

Re: [infinispan-dev] Infinispan URL format

> On 31 May 2016, at 13:33, Galder Zamarreño wrote: > >> In the past there has been talk of representing a connection to >> Infinispan using a URL, in particular for HotRod. >> The Hibernate OGM team is now working on adding NoSQL datasources to >> WildFly, and they've

Re: [infinispan-dev] Infinispan URL format

On 31/05/2016 13:33, Galder Zamarreño wrote: > Comments inline: > > -- > Galder Zamarreño > Infinispan, Red Hat > >> On 30 May 2016, at 09:46, Tristan Tarrant wrote: >> >> In the past there has been talk of representing a connection to >> Infinispan using a URL, in particular

Re: [infinispan-dev] Infinispan URL format

Comments inline: -- Galder Zamarreño Infinispan, Red Hat > On 30 May 2016, at 09:46, Tristan Tarrant wrote: > > In the past there has been talk of representing a connection to > Infinispan using a URL, in particular for HotRod. > The Hibernate OGM team is now working on

[infinispan-dev] Infinispan URL format

In the past there has been talk of representing a connection to Infinispan using a URL, in particular for HotRod. The Hibernate OGM team is now working on adding NoSQL datasources to WildFly, and they've asked for they should represent connections to various of these. For Hot Rod: