ZFN 0.3.0a1 is the first alpha release of the 0.3 series. The 0.3 series is designed to support more multi-user and security capabilities, such as accounts and ACLs. Download
This first alpha is not feature-complete yet. It supports accounts, secure WebDAV connections, and JSON-RPC appending. Several minor bugs from previous releases have been fixed. ZFN now depends on progtools, which is now a separate package.
ZFN 0.1.4 is the third bug-fix release for the ZFN 0.1 series. This release addresses issues with the JSON-RPC client. Download
ZFN 0.1.4 addresses two issues with the JSON-RPC client: the stat command's failure to recognize the -o option and the possibility of an upload overflow.
0.2.1, "Autumn Wind", is the second public release of the 0.2 series, fixing bugs from 0.2.0. Download
0.2.1 fixes several issues with the JSON-RPC interface, an issue with Genshi incompatibility, and the zfn-client stat command.
Also, ZFN 0.2.1 is now packaged with a Python 2.6 Egg for early Python 2.6 adopters.
ZFN 0.1.3, "Anderson", is the third bug-fix release for the ZFN 0.1 series. This release addresses issues with Genshi 0.5 and Internet Explorer compatibility. Download
ZFN 0.1.3 addresses a couple issues with Genshi: the dependency on Genshi was not declared in the installer, and newer versions of Genshi (namely 0.5.x) crashing on WebDAV access. As an added bonus, 0.1.3 is the first release to have a corresponding Python 2.6 egg.
The first public release in the 0.2 series, code-named "Double Day", has been released (after a brief illness). New features in this series include file locking, Mac write support, and iPhone optimization. Download
File locking is the most important feature in this release, and it was quite a shift inside ZFN's internals. To understand the need for this feature, we need to examine a common use example. Let's say John and Jane are using ZFN to share their files. John begins editing his thesis, "My Great Thesis.doc". While he's doing that, Jane realizes that John made a spelling mistake in his second paragraph, and saves the document. Then John saves his changes, overwriting Jane's spelling fix.
Without file locking, this kind of data loss would happen all the time. What file locking does is inform Jane when she tries to save that John is currently working on the file, and that she should try saving after he's done. For the most part, this will happen automatically.
This release also includes full Mac OS X read and write access to ZFN shares. Again, this is due to ZFN's support of file locking.
As an added bonus, ZFN's web interface now is optimized for the iPhone, so iPhone users can now view shared files without having to zoom and scroll through the page.
When installing the new version, the index server database schema has changed, so you will need to export the old database as an XML file (using the export-index.py script) and re-import it with the new version.
Hello, everyone. I apologize for the delay in releasing 0.2.0 final, but I was ill over the weekend and have recovered (nasty head cold!). Anyway, the release should be coming within the next 24 hours.
ZFN 0.2.0rc1, code-named "Good Access", is the final preview release in the 0.2 series providing small bug fixes and improvements. 0.2.0rc1 address an issue with command line options. Download
Remember, when installing the new release candidate from an existing 0.1 installation, the index server database schema has changed, so you will need to export the old database as an XML file (using the export-index.py script) and re-import it with the new version.
ZFN 0.2.0b2, code-named "Window Cleaner", is the second preview release in the 0.2 series providing small bug fixes and improvements. 0.2.0b2 address issues with page load times, Internet Explorer compatibility, and program dependencies. A new lock breaking script has been added for administrative convenience. Download
ZFN previously displayed the images in the web interface through a mechanism called Data URI, which was convenient for not cluttering the URI namespace, but was unfortunately incompatible with Internet Explorer. However, we found a way through URI-mangling to remove all data URIs, without the need for reserved names.
We also added a lock-breaking script, which is useful for administrators. If a file accidentally gets locked without being unlocked, the system administrator can now break the locks on a file. Without this script, a low-level WebDAV client needed to be used, or the database needed to be modified by-hand. This new script makes these methods obsolete.
Remember, when installing the new beta from an existing 0.1 installation, the index server database schema has changed, so you will need to export the old database as an XML file (using the export-index.py script) and re-import it with the new version.
The first preview release in the 0.2 series, code-named "Paperback Writer", has been unveiled. New features in this series include file locking, Mac write support, and iPhone optimization. Download
File locking is the most important feature in this release, and it was quite a shift inside ZFN's internals. To understand the need for this feature, we need to examine a common use example. Let's say John and Jane are using ZFN to share their files. John begins editing his thesis, "My Great Thesis.doc". While he's doing that, Jane realizes that John made a spelling mistake in his second paragraph, and saves the document. Then John saves his changes, overwriting Jane's spelling fix.
Without file locking, this kind of data loss would happen all the time. What file locking does is inform Jane when she tries to save that John is currently working on the file, and that she should try saving after he's done. For the most part, this will happen automatically.
This release also includes full Mac OS X read and write access to ZFN shares. Again, this is due to ZFN's support of file locking.
As an added bonus, ZFN's web interface now is optimized for the iPhone, so iPhone users can now view shared files without having to zoom and scroll through the page.
When installing the new beta, the index server database schema has changed, so you will need to export the old database as an XML file (using the export-index.py script) and re-import it with the new version.
