From: nf2 <nf...@sc...> - 2008-04-22 23:25:21
|
Miklos Szeredi wrote: >> What's the big deal if some applications can't save on ftpfs and display >> an error message when you hit the save button. FTP is not compatible >> with all file access modes - why shouldn't we be honest about that fact. >> >> i just changed ftpfs to return ENOTSUP on open(O_RDWR) and tested some apps: >> >> Kate, KWrite, Gimp, Inkscape, Nautilus (copying, moving files), VIM, >> NANO and Midnight Commander still work. I guess most KDE apps still work >> - because KIO doesn't encourage random file access. >> >> Unfortunately GEdit, DIA and Openoffice don't work, but as soon as they >> switch to a better abstraction layer (GIO), they probably would. >> >> I could live without GEdit on ftpfs (as there are lots of other >> editors), but Openoffice would certainly be nice. >> >> >> >> >>> But hey, you can prove me wrong. I just thing that _that_ ftpfs is >>> not the same ftpfs that provides the expected file semantics. >>> >>> So if you want to go this way, I'd suggest to at least optionally >>> provide buffering so that people may enable it if they want, dispite >>> it's problems. >>> >>> >> I agree, optionally enabling buffering should still be possible... >> Perhaps with a warning message that people should be careful with big files. >> > > Any news about this issue? I was reminded in the Novell bugzilla > #281052, that this is still not fixed. > > Norbert or Braga, do you have a new version of the patch I made > originally (or something else fixing this)? Or is there a new > curlftpfs release planned in the near future? > > Thanks, > Miklos > Hi Miklos, Well - i didn't work on this project recently (I focused on KIO-GIOBridge). The code of the "streaming writes only" version based on your patch is still here: http://code.google.com/p/curlftpfs/source/browse I don't think that optionally enabling buffered writing again would make of sense, cause of all the problems people have had. IMHO we have to accept that open read+write or open write+seek can not be mapped properly to FTP. Probably we should just release a new version based on the code in google svn. Regards, Norbert |