Releases for Bitcache

A second beta release for Drupal 6.x, and a highly recommended upgrade for users of all previous releases.

Changes since 6.x-1.0-beta1 (executive summary):

• There are important database changes. You must run update.php after upgrading to this release. In addition, you should also re-save the module's configuration (at admin/settings/bitcache).
• Alternate Bitcache repository backends (known as storage adapters) are now available, with MySQL, PostgreSQL, SQLite and GDBM databases supported in this release and Amazon S3 support in the works.
• The default repository created when Bitcache is first installed is now database-backed instead of file-system-backed. This should alleviate support overhead due to file system issues. For users upgrading from previous releases, the former file-system-backed default repository becomes editable and may be deleted in case it is not needed.
• Developers of dependent projects, such as File Framework, should take note that there have been many API changes (detailed in the CVS changelog). In many cases you can simplify your code, but in some cases your previous code may break if you had relied on the previously-valid assumption that repositories were file-system-backed.
• Numerous minor, and some major, bugs have been fixed, and usability and documentation improved overall.
• You can now set the order in which bitstream lookup proceeds through your configured repositories, as the rows on the repository management screen are now draggable in the same way as on many other Drupal administration screens.
• You can now manage bitstreams by repository, by clicking on the repository's title on the repository management screen.
• You can now prevent (overall, and based on user role) access to the bitstream index while still permitting access to individual bitstreams. This is particularly useful for large-scale Bitcache installations (containing hundreds of thousands of objects or more) where the index was becoming a performance problem.