[dsdp-tcf-dev] TCF client C API

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[dsdp-tcf-dev] TCF client C API

From: "Lu, Lianhao" <lianhao.lu@xxxxxxxxx>
Date: Fri, 2 Jul 2010 15:21:08 +0800
Accept-language: zh-CN, en-US
Acceptlanguage: zh-CN, en-US
Delivered-to: dsdp-tcf-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/dsdp-tcf-dev>
List-help: <mailto:dsdp-tcf-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/dsdp-tcf-dev>, <mailto:dsdp-tcf-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/dsdp-tcf-dev>, <mailto:dsdp-tcf-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AcsAbkg9ea8MAjSyQfqM4zY6nuNnsQZRYh1w
Thread-topic: TCF client C API

Hi guys,

It looks like the TCF specification defines the Framework API and service APIs in Java. Is it a requirement to follow this API for any TCF implementation? If so, how about the C language?(because the API is defined in Java). I compared the client Java API code and reference C agent code, it seems that they differ in the framework interface to some extent. We're planning to implement the TCF client C API, and wondering whether it is acceptable to the upstream if the client C API is based on the reference C agent code?

Best Regards,
----
Lianhao Lu
Software Engineer
Intel/SSG/OTC

Follow-Ups:
- RE: [dsdp-tcf-dev] TCF client C API
  - From: Tarassov, Eugene

References:
- [dsdp-tcf-dev] Using TCF with gdbserver
  - From: Lu, Lianhao

Prev by Date: [dsdp-tcf-dev] [Bug 318395] Fix and improve tracing of incoming CONF_SLAVES_INFO in java reference implementation
Next by Date: RE: [dsdp-tcf-dev] TCF client C API
Previous by thread: Re: [dsdp-tcf-dev] Using TCF with gdbserver
Next by thread: RE: [dsdp-tcf-dev] TCF client C API
Index(es):
- Date
- Thread

Breadcrumbs