I think a fileshare has a lot potential to make module use more accessible to anonymous and no trusts users to post theirs files after a scan virus process. I am thinking to force users to get theirs files scanned before the use of the upload process in the fileshare module.
Making the idea more simple, using the free web scanfile services for the Websites like Dr. Web: (http://www.freedrweb.com/for+web+sites/ ) can make this implementation possible in tow steeps:
1.- The uploaded file goes first to the Dr. Web Scan Virus file, if the response from the Dr. Web server is : “ No Clean” the processed file abort and if the response is: “Clean” go to second steep.
2.- Send the file to our server.

Comments

dboune’s picture

dboune commented

To add to the general idea, which may cover a basis for this and a few other feature requests.

It would be nice to have a general method of expansion for the base methods of access. This would allow modules to be built serving a number of needs.

For example, on 'download' of a directory object or selection of files, a file compression module could be hooked where appropriate and provide a compressed archive. On upload files could be first passed to an anti-virus scanner, a sorting tool, an archiver. An email notification module could make notifications on file upload or download (eek). File conversions from one type to another (document to PDF for example) could be plugged in.

Each idea expands the need for additional hooks, and something like a full-bore revision control system would take quite a few more hooks even to provide all the widgets and do-dads possibly needed. A good target for a much later stage in evolution, and a good direction to model in as much as that makes my head hurt.

The internal code related reason for doing something to support features like this in Fileshare isn't far off (hint hint), and it isn't likely in the best interest of Fileshare to internally expand too far from it's essential purpose which as I presently view it (feel free to help redesign my perspective if needed) is to provide a Drupal interface mechanism for storing, managing, and delivering filesystem objects.

What can be learned from other Drupal projects that will help here?

And so many other questions... Like.. can a wiki be a successful collaboration tool for module design in the Drupal development community.. and.. what is the policy (informal or otherwise) on php module dependencies for things like JSON, Fileinfo, recode .. and .. a dozen-dozen other things that will probably become trivial once understood.

Now that I've outlined some of my homework for this issue...