Re: lftp: would smb/smbclient support be aligned with project goals?
"Alexander V. Lukyanov" <[email protected]> Thu, 11 May 2017 09:43:24 +0300
| Newsgroups | gmane.network.lftp.user |
|---|---|
| Message-ID | <20170511064324.GA32052@lav-w> |
On Thu, Apr 20, 2017 at 03:04:00PM +0300, Alexander V. Lukyanov wrote: > On Wed, Apr 19, 2017 at 02:23:18PM +0200, Martin "eto" Misuth wrote: > > It occured to me, it might actually be more "proper" to add smb support to > > some proper ftp client - like lftp for example. All the user friendly > > machinery is there, so I guess this would require, "only" adding new backend. > > > > This seems making more sense, compared with adding proper "cui" > > (cli ui) layer to smbclient. > > Sure, it's the right way to go. > > > I would like to ask you what are thoughts about such proposition, would there > > be will for lftp author to have smb backend in the software? > > It is on TODO list for a long time. I think it can be done using > libsmbclient, but it must be either asynchronous (i.e. non-blocking), or > implemented as a separate process. Lftp is single-threaded, so adding a thread > might be hard. I think the best way to solve this is to create a FileAccess subclass for SMB protocol using blocking smbc_* calls, then implement a non-blocking proxy FileAccess (client and server) to pass necessary commands and results to/from a forked process. This way it would be easier to debug and the proxy will also be useful for other blocking libraries. -- Alexander. _______________________________________________ lftp mailing list [email protected] http://univ.uniyar.ac.ru/mailman/listinfo/lftp