Title: Message Title
|
|
|
|
Hi Richard
I agree that this change does not relate to curation tasks, I think I stated that above. The reason why I added this change to ClamScan though was to reuse the TCP virus checking that was already there and could be reused in the ingest. Perhaps the ClamScan class should be concerned with virus checking? But I do agree it should be disentangled with the curation logic.
Regards
George
|
|
|
|
|
|
|
The current virus checking during ingest is problematic for two reasons.
1) using the curation task to check for viruses means that all bitstreams are virus checked each time a bitstream is uploaded, see ClamScan.perform
2) using TCP to communicate with the clamav daemon is painfully slow for large bitstreams
This change allows the ingest to be con...
|
|
|
|
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
