Hi guys, >From past projects I've seen Sling used as more of a front controller (with >lots of perks) and then the resource as the controller (optional) or just a >simple view(script)/model(jcr) binding. Usually the controller being an >invoked java class or service.
This is how a number of projects I've been on have been structured. In this case, where would sling models fit in? -----Original Message----- From: Alexander Klimetschek [mailto:aklim...@adobe.com] Sent: Monday, January 13, 2014 2:27 PM To: dev@sling.apache.org Subject: Re: rename YAMF to Sling Models Sling Models _could_ be slightly confusing if you look at Sling as MVC: M = resources/jcr V = scripts/servlets C = sling engine Just my 2 cents, Alex On 11.01.2014, at 04:47, Carsten Ziegeler <cziege...@apache.org> wrote: > I'm +1 on the move, I'm not sure if Sling Models is a good name - as a > non-native speaker, the plural looks strange to me. But I don't oppose > if others are fine with it > > Carsten > > > 2014/1/10 Justin Edelson <jus...@justinedelson.com> > >> I'd like to move YAMF from my whiteboard in to extensions and rename >> it as Sling Models. >> >> https://issues.apache.org/jira/browse/SLING-3313 >> >> Please speak up if you have an objection. >> >> Regards, >> >> Justin >> > > > > -- > Carsten Ziegeler > cziege...@apache.org
