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.
Although these milestones are not definitive, there's always been a vision of what ZFN could be: a networking solution ubiquitous for stability and simplicity.
As we approach the coming months, I have a rough idea of where ZFN should have accomplished and what needs to be done.
Around the 0.3 release, I think full security features will be implemented, allowing a single ZFN share to be used by multiple people without fear of accidental (or purposeful) data loss.
By 0.4, we should have support for running multiple index servers that are sharing information as a single share, so that if one index server goes down, then users can just choose another server to work with. Our file locking mechanism has gone a long way to help this.
Around 0.5, I think having a web-based interface would be helpful to those without a WebDAV client, and would allow unique options for ZFN storage.
Eventually, there will be a better distribution method for ZFN. It's currently a bit difficult to install for the average user, and I hope that changes soon.
I hope you will help us make ZFN a better system by testing our software, or even just by coming up with ideas. Perhaps our 1.0 release will come sooner than anticipated.
As you can see, we just created a new blog for ZFN. I hope to use this blog to write about ZFN news, usage stories with ZFN, and upcoming features.
There isn't much on the blog yet, but this site is surely worth bookmarking if you're interested in what happens with ZFN.
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.
