On 10/1/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > ...I would prefer a name which somehow tells you what this object does....
Thinking about it, our Components currently have *two* major roles, right? 1) Render a Content object (SlingRenderer role?) 2) Process an incoming request which might modify the Content (SlingRequestHandler role?) Maybe the two roles should be split in distinct interfaces, to make naming easier? Also, I just noticed that ComponentRequest, for example, makes no reference to the Component interface. Makes me think that it could be called SlingRequest instead, and maybe (too busy to look now) there are other of our ComponentX types that might benefit from a similar renaming. Sorry if I'm not making things easier ;-) -Bertrand
