Jimmy,
Thanks for your clarification.
About the answer of my question #3:
=================================================================
> 3) D-Bus searching interface will not be exposed to application
developers, right? (P3, Sec4, Sub-Sec3)
> Furthermore, which part of interfaces will be exposed to application
developers and which part will not?
>
It will be still exposed (but through Tracker), not content manager.
Other application might still interact with Tracker, in fact, all other
Tracker-aware applications (like Deskbar, Nemo) communicates with
Tracker through D-BUS, otherwise, those application will break.
Content Manager will be just another lib that runs on top of tracker
that expose easier-to-use APIs. The intention is that Moblin
applications should call the Content Manager's interface. The D-BUS
interface in the design doc is what Tracker exposes. The Content
Manager is just a C library.
==============================================================
My understanding is the top level application has 3 ways to access the
functions of tracker/content mgr:
1. Call D-Bus interface
2. Call Tracker library (libtracker) C interface
3. Call wrapped content mgr library C interface
|--------------------|
-- | Applications |
| |--------------------|
| | |
| | (3)
| | |
| | |------------|
| | |Content Mgr |
| | |------------|
| (2) |
(1) | |
| | |------------|
| |- | Libtracker |
| |------------|
| |
| |
| |------------|
|----- | Libtracker |
|------------|
Is it right?
And if so, do the 3 ways provide same functionalities to applications?
Thanks,
Lei Y
_______________________________________________
dev mailing list
[email protected]
https://www.moblin.org/mailman/listinfo/dev
