[ https://issues.apache.org/jira/browse/SLING-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535175 ]
Bertrand Delacretaz commented on SLING-50: ------------------------------------------ Ok for dropping MimeTypeResolver > microsling: complete the SlingRequestContext information > -------------------------------------------------------- > > Key: SLING-50 > URL: https://issues.apache.org/jira/browse/SLING-50 > Project: Sling > Issue Type: Improvement > Components: microsling > Reporter: Bertrand Delacretaz > > Comparing microsling with the "full" Sling, the SlingRequestContext needs the > following additional information: > 1) ParsedRequestPath: extension, selectors, suffix, etc. > 2) SlingRequestParameters: a wrapper for the HttpServletRequest parameters, > that gives transparent access to parameters coming from multipart forms (at > least in the full Sling, but the interface must be the same). > 3) MimeTypeResolver: factor out the current SlingRequestContext.getMimeType() > method > The SlingRequestContext should as much as possible remain a container only, > and delegate parsing and other tasks to separate classes -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.