Le 18/11/2014 11:49, Von Dentz, Luiz a écrit :
Hi Dominig,
On Tue, Nov 18, 2014 at 12:01 PM, Dominig ar Foll (Intel OTC)
<[email protected]> wrote:
Le 18/11/2014 10:23, Von Dentz, Luiz a écrit :
Perhaps the CAPI context in IVI needs to be discussed first, as far I
know it is not compatible with GENIVI, in fact it is much more likely
that an IVI platform will use Tizen as middleware only since
manufactures like to have their own business logic on top. CAPI is
only really useful when it comes to user applications which is where
TCT tests apply, for middleware in my opinion it is probably more
important to stay GENIVI compliant.
Sorry by to be call Tizen you need to be certified for TCT is critical.
Now TCT are written per profile and so some flexibility is available,
nevertheless the value offered by Tizen is on top of Security and
Connectivity, the availability of a common Apps development process which
drags the requirement for Common APIs.
This has nothing to do with middleware, TCT test CAPI that is meant to
be used by applications, if you were to force middleware to use CAPI
you will probably end up having to rewrite many components that are
not Tizen specific, at least the communication daemons that talk to
each other using D-Bus directly and Im afraid there is many more
examples of that.
Luiz,
I already clarified in a previous emails that Tizen services (which
includes the daemons) could use direct communication with services which
are present in Common Base.
Direct connection with service which are service specific are to be used
more cautiously as it will stop cross profile portability.
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
