| Messaging Responsibilty can be: a) user, b) program, c) underlaying transport protocol. | |
Business people interest: the more implemented, the more complete, the better.
Academic people interest: list key problem areas and deal with them (AccessAuthentication might be a nice problem case). | |
| A strategy might be to monitor over many negotiations and then to try to figure out what people negotiate about and to try to find their preferences. Eg everybody uses Acknowledgements so we might rethink our implementation without Acks. | |
| But first implement the negotiation framework/architecture, THEN think about strategies. | |
| Build infrastructure with an interface first. | |
Then develop strategies which use that interface:
- default strategy: pass everything to the user. Also useful to test underlaying infrastructure.
- then potential strategy: implement one sample strategy that shows, that the framework is usable.
| |