Windows 10: how to remove an ftp server file for quick acess in file manager in windows 10

so if this occurs you have to just go to file options and then then click on the icon which mouse is hovering on and it while be removed from the quick access list.i hope it will help :

:)

 

FTP server - with file management/filtering ability

I've been looking (with not much success) to find an FTP server with the following features:

1./ Be able to filter file extensions, (e.g. *.pdf) and/or
2./ Be able to filter by filename using file wildcards, (e.g. X*.*, or Readme*.*)

Why?
Because I would like to give a number of people access to a folder, called, say, "database" and subfolders. Clients need to be able to "read only" the directory and sub-folders and SOME files. Whereas employees I want to be able to read and edit ALL files.

I only want the clients to be able to see files that are for their eyes, and not work in progress, or invoice/contract data, etc. For example, .pdf files they could see, but the source files, .doc, I dont want them to have access to. PLUS, if there are files I don't want them to see, e.g. files beginning with an "X", then they are not visible to the client.

Unfortunately, every FTP server seems to have directory rights, but NO features for filename/extension filtering. There must be such FTP servers... but I haven't found one yet.

Can you suggest one? Alternatively, what is the BEST FTP software you have found... and I will approach the developer to add a simple file filter to the FTP server.

 

FTP Server [With its own file Database] ?

I don't see a reason why the FTP needs to index the files before hand and not just read the directory when it is needed.

Of course the main reason against this is that any system like this wouldn't be up to date. Once the files system is indexed, if changes are made via something other than the FTP server itself the FTP server index would be outdate.

We see similar issues with Windows Indexing, a file can be deleted and it still shows up in the index, or a file can be created and it doesn't show up in the index.

Reading the actual file structure the moment it is requested insures that the file list is accurate, and really uses very little system resources.

 

FTP Server [With its own file Database] ?

Consider, if you would be running lefts 10-100 hard drive FTP. What happens, if for example user got for 'Folder A'

1. Hard drive has to power up because there is no cache
2. Hard drive has to read / list causes most of the problems for breaking hard drive.

^ Those 2 alone are reason to build hundreds of thousands costing softwares. So, why not simply caching code for FTP software.

To access File system index hardware has to be powered up = pretty big no no.
The FTP server index should be always out of date of course. timed checks only or manual update required to avoid bad copies from being added and generally it is good to know when newly added data would be in server instead of instant.

Yes, but I was referring that FTP Index should be working exactly like Windows Registry not like Windows Indexing. Directly on memory.

yes, this is true, but it fights everything I am searching for as index would read single location. reading 'on-site' would be hundreds of thousands of locations possibly which would raise every single hardware there would be in speed to do so.


-edit-

and on top of that I am testing here some of personal coding (trust me I suck at coding takes a lot even if I begin to try, hehe). Anyway, to build such database which would index would actually take less than 40 seconds for 300000 pictures with in 21000 folders structure. This list includes all nessessary information for <content>, Attributes, Size and could be shown clean out from server.

according to that calculation no matter how large the actual cache/index would be it would still be incredible fast and even this could be improved very very much considering with something like MySQL.