Hi all,
I posted a proposal for a definition of our Community Roles and
Processes in our Wiki [1]. The central points of this document are the
following:
* Every Committer is also a member of PPMC (Poddling PMC)
Some projects choose to clearly separate the roles of Committers and
[P]PMC
On Dec 13, 2007 9:24 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I posted a proposal for a definition of our Community Roles and
Processes in our Wiki [1]. The central points of this document are the
following:...
Thanks - I added some clarifications in there, and reworked some parts
On Dec 12, 2007 5:52 PM, Michael Marth [EMAIL PROTECTED] wrote:
Re issue 1):
we could have a 404 handler script that kicks in when a non-existing
resource is requested
Good idea. Do you have a suggestion about how to select which 404 script to use?
Assume I have dropped some scripts
On Dec 13, 2007 3:13 AM, Roy T. Fielding [EMAIL PROTECTED] wrote:
On Dec 12, 2007, at 1:10 PM, Bertrand Delacretaz wrote:
How about
/content/some/resource.html/s:version:1.4/s:lang:fr/somefile.pdf
where suffixes starting with s: are reserved for Sling usage?
yuck. A general
i think that our url processing is complicated enough and i
would really like to delegate everything beyond what we have
now to the application, until we find a usecase that is not
served well by delegating this kind of functionality to the
application.
You have convinced me. Definitely,
On Dec 12, 2007 10:52 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Bertrand Delacretaz wrote:
...That's why MicrojaxPostServlet uses a POST to /foo/* to mean create
new child node under /foo, and POST to /foo to mean update /foo.
Using PUT instead would be cleaner of course, but browsers
Bertrand Delacretaz wrote:
On Dec 12, 2007 10:52 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Bertrand Delacretaz wrote:
...That's why MicrojaxPostServlet uses a POST to /foo/* to mean create
new child node under /foo, and POST to /foo to mean update /foo.
Using PUT instead would be
Could the system look up the tree from the requested resource for the error
script? If no error script is found in the tree it could look for one in a
default location. For example, if a request is made for
/a/b/c/foo.html
Which results in a 404 the system would look in
/a/b/c
/a/b
/a
/error
