Re: [sleuthkit-users] What if a module fails to initialize

[Alex N. <ajn...@cs...>]

I vote 1, because one faulty module should not prevent the other modules' results, which may take a long time, from doing their work.  (Please believe me that this is not commentary on other current events.)

However, this requires the module framework have support for a results dependency graph.  This'll take some intelligent designer's time to get across gracefully to the end user if one module among many fails.  (I can say from experience that Make and Dot/GraphViz are not a simple solution.)

How do later modules in a pipeline specify that they need the results of an earlier module?

--Alex


On Oct 7, 2013, at 13:26 , Nanni Bassetti <dig...@gm...> wrote:

> My vote is for the number 2 :-)
> bye
> -- 
> Dr. Nanni Bassetti
> http://www.nannibassetti.com
> CAINE project manager - http://www.caine-live.net
> ------------------------------------------------------------------------------
> 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=60134791&iu=/4140/ostg.clktrk_______________________________________________
> sleuthkit-users mailing list
> https://lists.sourceforge.net/lists/listinfo/sleuthkit-users
> http://www.sleuthkit.org