cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Collen ...@hist.umn.edu>
Subject [RT] limiting access to a url by method
Date Fri, 13 Dec 2002 06:44:19 GMT
I've been thinking...  in a RESTful style architecture, one performs
"verbs" upon a certain URI, e.g. GET POST PUT or DELETE.  It seems to me
that Cocoon allows one to craft a REST-style application, and in fact it
lets one do it very easily.

However, I've noticed that Cocoon will respond to GETs or POSTs to
anything that it can match.  Does it make sense to deny requests to a
certain URI in a RESTful architecture?

When someone writes a servlet, they decide which methods to override;
doGet(), doPost(), and I believe doPut() and doDelete() are in there as
well, albeit a lot less likely to be used.  In essence, they are defining
what actions can be performed on the URI of the servlet.

What I'm getting at, is would it be at all useful to be able to limit the
things that Cocoon will respond to?  Perhaps something like an HttpMethod
selector?

Perhaps Cocoon already has this functionality and I just haven't run
across it yet :)


Time for bed.

Tony

Tony Collen -- tc@socsci.umn.edu
College of Liberal Arts   University of Minnesota, Minneapolis, West Bank


---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>


Mime
View raw message