Bertrand Delacretaz wrote: > Hi, > > I'm not sure if adding OCM mapping to microsling is worth the effort, > given that microsling is targeted at small apps. > > And more important, that might make understanding microsling quite harder. > > Currently, microsling allows for mapped objects via the > Resource.getData() method. > > If we agree that that's enough to allow "big Sling" to use OCM as it > does now, I'd suggest dropping the OCM plan for microsling, i.e. > closing SLING-76 as "wont' fix". > > WDYT?
Yepp, I think this makes sense. For ms based applications you most likely do not need/use OCM, so lets make this a plus for the "big Sling". Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
