Hi Guillaume,
That does sound like use cases well suitable for Sling. I would indeed not opt
for custom node types (yet), as simply using sling:resourceType is flexible and
allows quickly changing the content structure.
Indeed, authentication should not be an issue as well. Even it here was no
After spending 6 months working with AEM and MongoDB. I would be hesitant to
recommend it as a solution.
-Original Message-
From: Olaf [mailto:o...@x100.de]
Sent: Monday, November 16, 2015 10:49 AM
To: users@sling.apache.org
Subject: RE: Resource class vs CND
Hi Guillaume,
That does
Hi Jason,
That sounds interesting! Would you mind providing a bit more detail as to why
you would advise against it?
Regards,
Olaf
-Original Message-
From: Jason Bailey [mailto:jason.bai...@sas.com]
Sent: Montag, 16. November 2015 17:04
To: users@sling.apache.org
Subject: RE: Resource
Thank you Olaf for your answer.
I have currently little information about the app. What I know is that it
will mostly manage documents, organized like this:
- network (a dozen)
-- documents: around 1,500
--- pages: around 15,000 (total)
components (graphs, map, picture etc.): 1 to 4 per
