zipfs and write support

[Joel Uckelman]

Thus spake Alan Bateman:
>   
> Yes, to be portable, it is best to assume the file locking is advisory. 
> But, file locking isn't going to help when you are replacing the zip 
> file (which I assume is going to happen as it is based on 
> java.util.zip). An approach that I think I've suggested before is to use 
> a "server" to coordinate access. That would allow applications in 
> different VMs to access the "file system" concurrently. It could uses 
> the default file system as a temporary location for updates and re-build 
> the the zip file file when the file system is closed or the server is 
> shutdown. Clearly this is would be a more ambitious project and I'm just 
> mentioning it as a potential solution that someone might like to pursue.
> 

This sounds like a reasonable approach. But: That's quite some way beyond
what my project needs right now, so most likely it won't be me implementing
this.

-- 
J.