Re: Not-sticky sessions with Sling?
Alright, this is a deal breaker for our business (if sling absolutely requires sticky sessions). I hope you're not offended that I'm not 100% convinced yet. I understand you do development on the sling project and are well qualified on the topic. To be honest, however, I don't understand fully what you said in your last post and I also know that AEM 6.1 can do what I'd like, which is really just Sling+Oak. If they can do it, I don't understand why we can't. ref: https://docs.adobe.com/docs/en/aem/6-1/administer/security/encapsulated-token.html I'd hate to throw away all the awesome progress we've made with Sling so far when I know that AEM, which is just sling + jackrabbit, can accomplish app-server-agnostic authentication, and thus avoid sticky sessions. Although I don't understand this "head revision" that you've described, and that's inexperience on my part, I am confident that you're telling me that when there is only one Mongo instance in existence, and all Sling instances get data from it, that directly after "sling-instance-1" writes "myProperty=myValue" to the JCR, then "sling-instances-2" could get the value of "myProperty" from somewhere else - some old value. This only seems possible to me if one of the following is true: A) the Sling instances are caching values from Mongo (perhaps Sling or Oak is doing that?) B) There are separate versions of that property stored in Mongo (perhaps this is what you meant by the word revision) and it's possible for a sling-instance to be reading an old version of a property from Mongo. C) Mongo isn't consistent. We know from mongo documentation that C isn't true - Mongo is consistent when reading from the primary replica set. So it must be that A or B is going on? And if so, what is your guess about how AEM 6, which is Sling+Oak, avoids this pitfall when they very clearly support the stateless architecture (ie not-sticky) that I'm planning? -- View this message in context: http://apache-sling.73963.n3.nabble.com/Not-sticky-sessions-with-Sling-tp4069530p4069605.html Sent from the Sling - Users mailing list archive at Nabble.com.
Re: uses for Sling
Hello Jason, We used it for an extranet for sales people. The company has different brands, each brands contains different products and then the country is divided in regions, sectors and target units. The nodes tree was then convenient for this data structure. We have then different "documents" (nodes) which contains "pages" and "components" (also nodes, like text components, images, tables etc). A document is pre-filled by the management with some data (charts, goals etc.), then for some component each user can provide its own data (for instance update the text of a text component). We found Sling useful because we don't have to architecture the data structure for future components. Let's say we want to provide a Youtube component that will display a Youtube video in the document, we just create a new node with Sling:resourceType = myapp/component/youtube, set the video URL, and add a specific view for this component. Before, it was all stored in a database and not very flexible. The front is just an Angular site sending requests to the Sling REST API, as it's ready to use. Users/groups and privileges management was also a good point as it's also ready to use and flexible. We didn't develop a lot of things for content management. I was a complete Sling newbie at the beginning of the project but with some spamming to the mailing list it worked pretty well. As lots of documents have the same skeleton, we just created a tool to do bulk updates on nodes but that's pretty much it. Regards, Guillaume On Fri, Jan 13, 2017 at 4:28 PM, Jason Baileywrote: > I know that Sling is used for 2 downstream CMS applications. > I was wondering if anyone could share other use cases that they have found > Sling to be useful for. > > Thanks. >
uses for Sling
I know that Sling is used for 2 downstream CMS applications. I was wondering if anyone could share other use cases that they have found Sling to be useful for. Thanks.
Re: How to change run mode in Sling8
Hi Lance, On Fri, Jan 13, 2017 at 1:54 AM, lancedolanwrote: > ...It's just some text files that neatly describe > which OSGI bundles and configurations (including run modes) you'd like > present in a new .war file which is then built using *actual* sling > artifacts from completely different projects Indeed! There are some docs about this at https://sling.apache.org/documentation/development/slingstart.html (and patches welcome on that as usual) -Bertrand