List Info

Thread: Who defines the "request URL"




Who defines the "request URL"
user name
2007-02-01 11:06:11
I THINK IT MAKES SENSE FOR SPECIFICATIONS THAT USE THE
ACCESS CONTROL  
MECHANISM TO CAREFULLY DEFINE WHAT THE "REQUEST
URL" IS. IT'S NOT CLEAR TO  
ME THAT IT BE DONE IN A GENERIC WAY WITHIN THE ACCESS
CONTROL  
SPECIFICATION ITSELF. SUGGESTIONS WELCOME. LATEST VERSION OF
THE DRAFT:

HTTP://DEV.W3.ORG/CVSWEB/~CHECKOUT~/2006/WAF/ACCESS-CONTROL/
OVERVIEW.HTML?CONTENT-TYPE=TEXT/HTML;%20CHARSET=UTF-8


(THE "REQUEST URL" IS THE LOCATION OF THE OBJECT
FROM WHICH THE REQUEST TO  
THE RESOURCE, TO WHICH THE ACCESS CONTROL READ POLICY
APPLIES, ORIGINATES.)


-- 
ANNE VAN KESTEREN
<HTTP://ANNEVANKESTEREN.NL/>
<HTTP://WWW.OPERA.COM/>


Created: (JCR-728) Automatic MIME type detection
user name
2007-02-01 11:49:05
Automatic MIME type detection
-----------------------------

                 Key: JCR-728
                 URL: https:/
/issues.apache.org/jira/browse/JCR-728
             Project: Jackrabbit
          Issue Type: Improvement
          Components: indexing
            Reporter: Jukka Zitting
            Priority: Minor


Currently only the jcr:mimeType property is used to
determine the MIME type and thus the applicable text
extractor to use for indexing a document. If the
jcr:mimeType property is not available or is set to a
generic value like "application/octet-stream",
then the indexer could also use some heuristics based on the
node name or magic numbers within the binary stream to
determine the type of the document.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.


[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )