> > > ...I was actually thinking about making JCR observers scriptable as well. > > This is in fact a very interesting extension. Still I would strongly > > suggest to not implement this in microsling but in Sling.... > Why? > Repository events are a very important differentiator of JCR as > compared to other content storage mechanisms, so I don't see why this > shouldn't be in microsling. As I said above, on top of being an entry > point to Sling, microsling can also be an entry point for JCR, to help > people discover it in an easy to use scriptable environment. I agree that this is a great feature of JCR and needs to be exposed. ... and the simplicity of the usage of observation is just stunning, so i love it.
However, I would agree with Felix in the sense that it probably is possible to write a lot of "microsling" worthy apps without having the observation feature. So i guess I would also put it rather low on a priority list and wait for someone needs it. (Which probably will happen sooner than later) I think it is great though the way we "specified" it in this thread and we should keep it this simple wherever we implement it. regards, david
