Changes between Version 1 and Version 2 of ApertureDataObjectFile

Timestamp:

10/20/05 14:58:28 (19 years ago)

Author:

sauermann

Comment:

--

ApertureDataObjectFile

@@ +1 @@
+Mimetypes: Chirs suggest to leave it partially in. my idea is that the crawler only returns what the data source returns. if a specific data source returns mimetypes (e.g. some webservers), return that, but else make no effort to determine it. after all it depends on the use case whether you need it at all and what the best way is to fill in missing values. our experience btw is that you should never trust the mime type returned by a webserver ;) in our apps we will always use a magic number-based mechanism
+
+Leo: to be used, we can do it as convenient as possible. Meaning, the DataObjectFile has a getMimetype() method which promises to use all tricks that exist. If you don't call getMimetype(), no processing power spilt. If you call it, it guarantees to have done all tricks already (which is very convenient and a useful feaute of the Aperture framework).
+
+
 {{{
 #!java
@@ -41 +46 @@
         /**
          * what is the mime-type of the content, if there is content?
-         * This is set by the DataAccessor
-         * @return null or a mimetype identifier like "text/plain"
+         * This is set by the DataAccessor. This method may cause complicated mimetype detection,
+         * like looking at the http mime-type, file extensions, magic bytes inside the file-stream.
+         * @return a mimetype identifier like "text/plain" or null if the 
+         * identifier cannot be determined, even using all tricks available.
          */
         public String getContentMimeType();