Copyright (c) 2007-2019 Wind River Systems, Inc. and others. Made available under the EPL 2.0
Agent portion made available under your choice of EPL 2.0 or EDL v1.0 dual-license.
Direct comments, questions to the tcf-dev@eclipse.org mailing list
| Version | Date | Change |
|---|---|---|
| 0.1 | 2008-01-10 | Initial contribution |
| 1.0 | 2008-05-06 | Approved |
TCF communication model is based on the idea of services. A service is a group of related commands, events and semantics. For example, Memory Service defines group of command and events for reading and writing target memory. Service definitions are not part of the framework specification, and new services are expected to be defined by developers of tools and target agents. Defenitions of standard services are provided to achieve certain level of compatibility between tools and targets.
Format of the protocol messages is defined by syntax rules, see Syntax Rules Notation.
TCF standard services use JSON for message encoding, see JSON - Preferred Marshaling.
TCF standard services use same format for error reporting, see Error Report Format.