Sync startup/finish semantics

[GoogleCodeExporter]

We need to formalize the startup / finish semantics of sync

Current Design?
engine.start() {
  // Run syncs as needed under sync condition
}

Proposal 1:
engine.start() {
  // Pre-run all Syncs

  // --Engine starts running--
  // Run syncs as needed under sync condition 
  // --Engine finishes--

  // Post-run all Syncs
}

Proposal 2:
engine.start() {
  // --Engine starts running--
  // Run syncs as needed under sync condition 
  // --Engine finishes--

  // Post-run all Syncs
}

This creates an issue in the sampler since I can't say what will have been 
sampled in the first "joint sample."

Original issue reported on code.google.com by Joseph.E.Gonzalez on 21 Apr 2011 at 5:15

[GoogleCodeExporter]

Shifted priority to High. To get done by next release.

Original comment by yucheng...@gmail.com on 17 Jun 2011 at 6:43

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by yucheng...@gmail.com on 16 Nov 2012 at 11:30

• Changed state: Done