Re: Support REST-ful APIs

On Apr 7, 2014, at 12:24 AM, Felix Meschberger wrote: TL;DR: Use Accept header to set request's selectors and extension. So an example Accept content type of application/x-players+json would set the selector string to players and the extension to json. We always touted Sling to be a

Re: Support REST-ful APIs

Thanks Roy for clarifying things. I think what it boils down to is that the only real thing that you'd want to move from the sling url (path info) to an accept header would be the extension = mimetype, in case you support multiple variants (say html, json, xml, ...). The selector part is

[jira] [Created] (SLING-3502) Main job queue is not properly outdated

Marc Pfaff created SLING-3502: - Summary: Main job queue is not properly outdated Key: SLING-3502 URL: https://issues.apache.org/jira/browse/SLING-3502 Project: Sling Issue Type: Bug

[jira] [Commented] (SLING-3502) Main job queue is not properly outdated

[ https://issues.apache.org/jira/browse/SLING-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968630#comment-13968630 ] Marc Pfaff commented on SLING-3502: --- IMHO that's a regression of SLING-3381. Main job

[jira] [Updated] (SLING-3502) Main job queue is not properly outdated

[ https://issues.apache.org/jira/browse/SLING-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Pfaff updated SLING-3502: -- Attachment: SLING-3502.patch Attaching patch. This patch makes sure, the implicit main queue is