Re: Not-sticky sessions with Sling?

Hi, On Mon, Jan 16, 2017 at 9:16 PM, lancedolan wrote: > ...this probably shoots down our entire Sling > proof of concept project... That would be a pity, as I suppose you're starting to like Sling now ;-) > ...Is there any way > to force all reads to read the most

Re: Not-sticky sessions with Sling?

On Tue, Jan 17, 2017 at 1:46 AM, lancedolan wrote: > It's ironic that the cluster which involves multiple datastores (tar), and > thus should have a harder time being consistent, is the one that can > accomplish consistency.. Thats not how it is. Cluster which involves

RE: Bad asset resource resolving

no, the basics of resource resolution have not change recently - a resource with multiple dots in it's resource name (like /content/sling.logo.png) should always be resolvable by this name. and it works as expected when i reproduce the steps you describe (copy to /content/sling.logo.png). i

Re: Not-sticky sessions with Sling?

This is really disappointing for us. Through this revisioning, Oak has turned a datastore that is consistent by default into a datastore that is not :p It's ironic that the cluster which involves multiple datastores (tar), and thus should have a harder time being consistent, is the one that can

Bad asset resource resolving

Hi all, It seems that the way assets are resolved has changed a little. When an asset contains an additional . (dot) it can't be resolved anymore to the actual asset resource. e.g. /content/my.asset.pdf resolves to /content/my.pdf rather than the expected path. As a simple test you can copy the