> > I've not looked at the policy spec for ages but none of those sound > like we'd need actual runtime support for things like transactions, > async, noListener etc so it seems like we may be able to get them all > passing now with whats there in the model already, does that sound > right or can someone see things that they know wont be able to be > working?
I don't really know how noListener and asynchInvocation will be implemented although they do imply specific configuration to the runtime, i.e. builder changes. Unless we need optional configuration over and above this then a policy set is not required. Too early to say though. If we decided that a policy set is not required then we still need a way to process these intents so that we don't get an unsatisfied intent error. If we don't provide runtime for transactions we'll get an unstatisfied intent error. However the transaction policies are being worked on and there is probably enough there now to get through the tests. We do need to make sure the transaction policy modules are available as dependencies. Simon
