[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dsdp-tcf-dev] TCF client C API
|
True, but I think it would be beneficial to the community if we
provided an API in C that could be reused for Tools and Services
written in C and/or C++. Then they could ensure they are properly
following the protocol. Does the reference agent, which is written in
C, have that?
On Fri, Jul 2, 2010 at 12:40 PM, Tarassov, Eugene
<eugene.tarassov@xxxxxxxxxxxxx> wrote:
> Hi Lianhao,
>
> No, It is not a requirement that any TCF implementation follow same API.
> Our goal is standard protocol, implementation can be different.
>
> Regards,
> Eugene
>
> -----Original Message-----
> From: dsdp-tcf-dev-bounces@xxxxxxxxxxx
> [mailto:dsdp-tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Lu, Lianhao
> Sent: Friday, July 02, 2010 12:21 AM
> To: DSDP TCF dev list
> Subject: [dsdp-tcf-dev] 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
>
>
> _______________________________________________
> dsdp-tcf-dev mailing list
> dsdp-tcf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tcf-dev
> _______________________________________________
> dsdp-tcf-dev mailing list
> dsdp-tcf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tcf-dev
>
