Re: [xwiki-devs] [Proposal] Action Module revisited - take 2

I'm glad to see this moving again. For those who weren't watching before, the story of actions was that they were partially developed and we wanted smooth pluggable support for portlet and servlet without losing any features of either. I could not find a way to implement this and development stalled. q1: Is portlet support still a requirement and if so, what is the balance we want to strike between features which don't work for one of the two paradigms or features which are missing completely to keep the actions portable? q2: What is the relationship between an action and a REST request? I can imagine in an ideal world that skin/html could actually just be a form in which a rest response would be transported. q3: Will this go through a period as an installable extension before it lands in XE? To me this is a big deal because we need to really start walking the walk regarding slick'n'slim and moving things out of XWiki's "core". q4: Where do we want to draw the line between simplicity and flexibility? When Servlets were devised flexibility was very popular but today you see frameworks advertising their most simple interfaces with "get started today" and tiny code snippets [1] [2]. Stated otherwise: do filters actually make sense at this point? Personally I'd YAGNI the filters and shoot for simple. These questions are food for thought but in general, I want to do whatever I can to sign off on this because I don't want to paint the bikeshed here, especially when I'm not writing the actual code. Thanks, Caleb [1] http://www.sinatrarb.com/ [2] http://nodejs.org/#column1 On 02/04/2014 09:11 AM, vincent(a)massol.net wrote: