True parallel operation execution isn't possible with the current appraoch

[james-nesbitt]

The current operation implementation doesn't allow you to execute long running operations forked:

1. setting prameters would overwrite parameters on an executing operation
2. no proper go method for tracking when an operation ends.

Should these things be more built into the base API

[james-nesbitt]

This is an understood issue.

The current implementation was a first run at having a system that could allow operations to be threaded, but there are some mistakes that were made.

There are two attempts art refactoring for such implementation, but both would require significant refactoring of all handlers and API implementations.

While this is a significant issue, it doesn't block the majority of the current effort, which doesn't need thread-safe implementation.

[james-nesbitt]

concurrent operations may benefit from the following ideas:

1. perhaps properties should be attached to the result, then concurrent channel based writing could be attached using a result that has capabilities for it. A custom concurrent result struct could be built that would receive properties, create copies, and create channels for goroutine writing.

This would have pros and cons:

• pro: better concurrent handling of properties
• con: an operation implementer would have 2 Properties structs, one which was fed into the operation, and one from results. This may actually be a 'pro' for cases where you would re-use the operation concurrently.