Hi all,
Currently the SlingServlet is a very simple interface defining doXXX
methods for some HTTP request methods and a canProcess method to ask
whether the SlingServlet is willing to process the request. I think,
this interface is not required as is. I discussed this quickly with
Bertrand
Hi,
On 10/16/07, Felix Meschberger [EMAIL PROTECTED] wrote:
What is your opinion on this: A separate SlingServlet interface/class
hieararchy or going along the lines of the HttpServlet (yet doing it
better with respect to non-core HTTP methods) ?
I'd go with HttpServlet, see my previous email
On 10/16/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...What is your opinion on this: A separate SlingServlet interface/class
hieararchy or going along the lines of the HttpServlet (yet doing it
better with respect to non-core HTTP methods) ?...
I tend to agree with you guys about using
Jukka Zitting wrote:
Hi,
On 10/16/07, Felix Meschberger [EMAIL PROTECTED] wrote:
What is your opinion on this: A separate SlingServlet interface/class
hieararchy or going along the lines of the HttpServlet (yet doing it
better with respect to non-core HTTP methods) ?
I'd go with