Thomas P. Fuller wrote:
With regard to #3.
Why not have both and make the threading api more or
less a configuration issue?
We should be able to decouple framework from the
specific api via an interface -- and this could be
handy down the road if something new becomes available
which has an advantage not present in the Oswego or
1.5 packages.
This same idea is expressed in point 4 below.
Doh! Good catch - if we get the interface right, the implementation can
be varied making #3 a non-issue.
--
Jeremy
