title: Class structure for future multi-threading
body: <p>I have an algorithm that runs on a large problem set. It reads the problem instance, 
  then runs the algorithm on that problem read from the file. </p>
  
  <p>The solution space can be partitioned (can be split into disjoint sets that cover the entire space).
  That is, the algorithm can take advantage of concurrency/multi-threading. </p>
  
  <p>It isn't doing any concurrent processing at the moment. 
  However, for the latter enhancements, i'm trying to make the class structured for this. </p>
  
  <p>One thing i'm doing is: </p>
  
  <p>keeping the field members &amp; methods that read the problem, and have no affect or are affected by the solution instances as <code>static</code></p>
  
  <p>&amp; </p>
  
  <p>the rest of the members-- the field variables specific to each solution space &amp; methods that run on solution spaces as <code>non-static</code>. </p>
  
  <p>Is the anything more I should do for future concurrency at this point?</p>
  
  <p>TIA. </p>