I seem to have failed to get my point across when I last visited
Basel and we talked about what can and cannot be done in a selector.
The original Web design notes forbid the use of GET for any action
that is considered to have side-effects, because such an
implementation allows users to be
On Oct 16, 2007, at 1:18 AM, Bertrand Delacretaz wrote:
On 10/15/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
...We could for example define that adding a slingMethod=PUT
parameter
to the request causes SlingServlet.doPut to be called instead of
doPost
To clarify, note that I
On Nov 26, 2007, at 8:15 AM, [EMAIL PROTECTED] wrote:
SLING-98 Migrate JSP scripting support
+ plus include Jasper Compiler and EL implementation
Ouch. Just out of curiosity, why do we need the source of jasper?
Is it to replace the back-end storage bits with JCR? Would it be
possible to
On Nov 30, 2007, at 1:32 AM, Bertrand Delacretaz wrote:
I did propose a discover microsling talk, that we meant to give
together with Felix.
It has not been accepted for the main track, but the planners suggest
proposing it for the fast feather track (that's shorter 15 minute
talks).
Was
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 principle of web design is that you shouldn't
be able to tell how a server is
[
https://issues.apache.org/jira/browse/SLING-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553455
]
Roy T. Fielding commented on SLING-53:
--
This needs to be very well documented. Some companies will consider
I think executing a script upon GET of a URI should only be possible
on generated (symlink or alias) URIs that are specifically configured
for that purpose and have separate access control from the URIs used
to edit/view those scripts. This follows the same practice used in
Web servers with CGI
What about using extensions to specify the desired behaviour?
This could look as follows:
POST to /foo- 200 OK and a XHTML representation
POST to /foo.html - 200 OK and a XHTML representation
POST to /foo.xml- correct response codes and a
XML
On May 5, 2008, at 11:07 AM, Felix Meschberger wrote:
Am Montag, den 05.05.2008, 16:58 +0200 schrieb Bertrand Delacretaz:
On Mon, May 5, 2008 at 4:24 PM, Felix Meschberger
[EMAIL PROTECTED] wrote:
If :status is alwaysok, the 200
response is sent
According to SLING-422, this is
[
https://issues.apache.org/jira/browse/SLING-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595341#action_12595341
]
Roy T. Fielding commented on SLING-438:
---
Naming anything core is unwise if you expect
On May 28, 2008, at 2:16 PM, Jukka Zitting wrote:
On Thu, May 29, 2008 at 12:13 AM, Roy T. Fielding
[EMAIL PROTECTED] wrote:
I thought that was because Jukka disabled Continuum.
I did that only for Jackrabbit. Haven't touched any Sling infra.
I think there is something wrong with the Sling
Unnecessary whitespace, headers, horizontal rules, page breaks,
instructions on how to edit, and related nonsense should never
appear in the NOTICE file that is required by our license to be
displayed by downstream binary distributions like an About box.
Roy
On Jun 2, 2008, at 8:10 AM,
On Jun 3, 2008, at 5:41 AM, Felix Meschberger wrote:
Am Dienstag, den 03.06.2008, 14:32 +0200 schrieb Bertrand Delacretaz:
On Tue, Jun 3, 2008 at 1:52 PM, Bertrand Delacretaz
[EMAIL PROTECTED] wrote:
...I'm generating the NOTICEs as we speak, ETA 30 minutes...
Done (took 34 minutes, sorry
On Jun 4, 2008, at 5:41 AM, Carsten Ziegeler wrote:
the following line needs to be added to the notice file in the
commons/json module:
This product includes software developed at http://json.org.
NOTICE is only for attributions that are required by their corresponding
copyright license or
On Jun 3, 2008, at 11:45 PM, Bertrand Delacretaz wrote:
On Wed, Jun 4, 2008 at 12:35 AM, Roy T. Fielding
[EMAIL PROTECTED] wrote:
...I'd rather have a set of hand-edited NOTICE files that accurately
reflect each of the release packages
I see your point, and thanks for your changes
On Jun 11, 2008, at 1:48 AM, Felix Meschberger wrote:
Am Mittwoch, den 11.06.2008, 10:10 +0200 schrieb Carsten Ziegeler:
Bertrand Delacretaz wrote:
Note also that the current notice files include several things that,
according to Roy in his revision 662927 changes, do not require
notices.
On Jun 11, 2008, at 1:33 AM, Jukka Zitting wrote:
On Wed, Jun 11, 2008 at 10:40 AM, Carsten Ziegeler
[EMAIL PROTECTED] wrote:
It would be great if some people could check everything, so that
we're safe
for our upcomming release.
There's FeedParser license information at the end of
On Jun 11, 2008, at 10:43 PM, Jukka Zitting wrote:
On Thu, Jun 12, 2008 at 7:46 AM, Roy T. Fielding
[EMAIL PROTECTED] wrote:
I am struggling to understand what is going on here. LICENSE and
NOTICE
refer to the copyrightable material in *this* package. Surely we
don't
distribute Derby
On Jun 12, 2008, at 12:18 AM, Carsten Ziegeler wrote:
I just talked with Felix offline about this and we came up with the
following solution which should meet the requirements.
As Roy points out we have to distinguish between source and binary
distributions (and yes, the ASF does only
On Jun 13, 2008, at 12:54 AM, Jukka Zitting wrote:
- The src/main/resources/META-INF(LICENSE file has no reference
to the LICENSE.slf4j file
The LICENSE.* files seem pretty obvious, so I'm not sure if the
reference is really needed. I'd say we either leave it as is (no
references), or include
Umm, this is incomplete. Apache doesn't redistribute the JCR jar under
the Specification License. Apache can distribute the binary under the
additional terms that are posted on the Day maven site
http://www.day.com/maven/jsr170/jars/LICENSE.txt
so that should be included in the launchpad
[
https://issues.apache.org/jira/browse/SLING-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610336#action_12610336
]
Roy T. Fielding commented on SLING-562:
---
I think using segment parameters would
[
https://issues.apache.org/jira/browse/SLING-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610354#action_12610354
]
Roy T. Fielding commented on SLING-562:
---
They are just a part of the URI path
Sounds like an easy way to bypass delegated security.
I don't like the idea of sprinkling root-level aliases
all over the content tree. I think it would be incredibly
complex and impossible to maintain over time, and not even
remotely scalable for virtual hosting setups.
I think that Sling
On Nov 23, 2008, at 1:42 PM, Felix Meschberger wrote:
Roy T. Fielding schrieb:
I think that Sling should use a content tree to establish the
root mappings; e.g.,
/etc/map/{scheme}/{host.port}/{uri_path}
with the default contents being
/etc/map/http/example.com.80
On Nov 24, 2008, at 5:06 AM, Felix Meschberger wrote:
Better yet, we might do regular expression matching and referencing:
/etc/map/http/www.(.)*.com.80/
+-- sling:contentPrefix = /content/sites/$1/
Question, though, is how to get these strings into the
[
https://issues.apache.org/jira/browse/SLING-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708587#action_12708587
]
Roy T. Fielding commented on SLING-964:
---
Should this be fixed in Sling or in Commons
On May 12, 2009, at 12:40 AM, Bertrand Delacretaz wrote:
On Mon, May 11, 2009 at 10:29 PM, Roy T. Fielding
field...@gbiv.com wrote:
On May 11, 2009, at 12:03 PM, Felix Meschberger wrote:
Carsten and I have been reasoning about the releases in the future,
mainly the ones for end-users who
On May 24, 2009, at 7:36 AM, Andreas Hartmann wrote:
Hi J. Aaron,
thanks for the pointer!
J Aaron Farr schrieb:
There's a thread starting on infrastructure apache.org about the
requirements for a CMS for the ASF. Here's a snippet from Paul:
Is this archive accessible to the public? I
29 matches
Mail list logo
