Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [dsdp-tcf-dev] TCF client C API

How about the C version of the framework that is tailored for tools development? Should it be similar to Java interface defined the TCF specification? Unlike C++, there's a big gap between C and Java.

- Lianhao

> -----Original Message-----
> From: dsdp-tcf-dev-bounces@xxxxxxxxxxx
> [mailto:dsdp-tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Tarassov, Eugene
> Sent: Saturday, July 03, 2010 1:52 AM
> To: DSDP TCF dev list
> Subject: RE: [dsdp-tcf-dev] TCF client C API
> 
> Since the agent is supposed to run in embedded environment, it is
> important to keep its size small.
> So, agent APIs are less abstract, more practical and rather
> minimalistic. In particular, unlike in Java, in C we do not define APIs
> for the protocol itself - for individual commands, events etc.
> In fact, I'm already concerned about the agent getting too fat and
> consider options of getting it thinner.
> 
> At the same time, it would be good to have C++ version of the framework
> that is tailored for tools development and similar to Java version in
> abstraction level and scope.
> 
> Eugene
> -----Original Message-----
> From: dsdp-tcf-dev-bounces@xxxxxxxxxxx
> [mailto:dsdp-tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
> Sent: Friday, July 02, 2010 9:50 AM
> To: DSDP TCF dev list
> Subject: 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
> >
> _______________________________________________
> 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


Back to the top