Community
Participate
Working Groups
In 4.2 we have different agent controllers on different platforms. One supports the old API's and a new API - but not both at the same time. When writing a new agent or client, a decision must be made as to which API to use. The choice of API impacts whether the new client/agent will work with an existing client/agent. Need to document the trade offs and AC roadmap to assist in making these decisions.
Deferred as part of bulk transfer of less severe bugs to 4.2 I3. Some of the bugs were not previously triaged by the owners. Owners should ensure these bugs are triaged and properly targed to I3.
Documentation, so pushing to i4.
I have written the document and passed it through several technical reviews. Needs final formatting and committing to an appropriate docs location, so re-assigning to Dale.
Modified title.
Documents formatted and Committed to CVS at \org.eclipse.tptp.platform.agentcontroller.doc.isv\concepts\ac\c_dc_framework_intro.html on 6/5/06.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.