README.txt
上传用户:zhongxx05
上传日期:2007-06-06
资源大小:33641k
文件大小:3k
- README.txt for HTTPLite Filesystem plugin
- -----------------------------------------
- INTRO:
- This document describes how to build HTTPLite. HTTPLite is a HTTP FileSystem Plugin.
- Currently it only supports HTTP/1.0. Also, it supports very basic features leaving
- advanced ones like redirection, proxy handling, HTTP/1.1 for the future. As a result,
- the plugin is small (hence the suffix "Lite"). It is expected that all the advanced
- features will be built by extending the current design of the plugin.
- The plugin, as it exists, now is well suited for use on mobile devices because of
- its small size resource requirements.
- BUILD CONFIGURATION:
- Choose the build target as FILESYSTEM_HTTPLITE.
- PROFILE:
- The plugin uses a cache to store some of the clip data so that it can serve requestes for
- data a small time in the future/past (the exact values depend on the size of the cache,
- which can be configured). There are two types of caches - (1) MemCacheObj which uses only
- memory for storing info, and (2) FileCacheObj - which uses both memory as well as the
- local file system for caching. The plugin uses only one of them. Which one to support should
- be decided at compile tie itself. If the profile for the device contains the feature
- "HELIX_FEATURE_HTTP_FILECACHE", then the plugin is built so that it uses the FileCacheObj,
- else it is build to use the MemCacheObj.
- RUNTIME CACHE CONFIGURATION:
- It's not automatically guarenteed that a FileCacheObj would be used if the feature
- "HELIX_FEATURE_HTTP_FILECACHE" is set during build time. If the user decides that he
- doesn't want to cache media clips on his hard disk, the HTTPLite plugin will then use
- the MemCacheObj instead of the FileCacheObj. The user can set his preferences in this
- regard by using the UI. Thus, FileCacheObj is used only when BOTH of the following are
- true:
- (1) "HELIX_FEATURE_HTTP_FILECACHE" was enabled during build, AND
- (2) User has set his preferences (via the player UI) to cache on the disk.
- If atleast one of them is not true, then the plugin uses MemCacheObj. Note that for
- compilation, the source for MemCacheObj is included no matter what. Whether the source
- for FileCacheObj is included or not depends on the "HELIX_FEATURE_HTTP_FILECACHE" feature.
- MORE DOCUMENTATION:
- See the associated UML documentation and informal description of design present in the
- directory Documentation. The UML documentation consists of the class and sequence diagrams.
- They are present as ".xmi" files and can be viewed using MagicDraw software. The informal
- description is present as a word document.