Thanks for more clarification. Then, Service Framework is an enabler and there's no ready-to-use "service" available out of box in Qt Mobility, right?
-koichi On Tue, Feb 1, 2011 at 9:44 AM, Srikanth <[email protected]>wrote: > * > ->So Service Framework is for communicating between two or more Qt > applications (or at least processes)* > Not exactly. You have QProcess for that, so why SFW? SFW is to create a > service and let many clients access it. The important part is "access". The > more pain free you make it, the better ease of use for developers. Hence > read SFW as a package of service implementation and discovery. > > *->but NOT for a Qt application to find and use system services. Is this > correct?* > Well, it depends on how you interpret a service. You can write a file > access service around filesystem, that provides all file related actions. I > can interpret that service as a system service wrapper! > > On Tue, Feb 1, 2011 at 11:45 AM, Koichi Mori <[email protected]>wrote: > >> I see. So Service Framework is for communicating between two or more Qt >> applications (or at least processes), but NOT for a Qt application to find >> and use system services. Is this correct? >> >> -koichi >> >> On Wed, Jan 26, 2011 at 12:35 AM, Srikanth >> <[email protected]>wrote: >> >>> Service Framework (SFW) is a generic inter-process communication >>> mechanism targeting all Qt supported platforms. The basic problem is that >>> each platform has its own IPC mechanism and with QtMobility Qt aims to >>> simplify it such that a service provider runs as a service (mostly a >>> separate process) and all clients access the service with a very simple >>> discover mechanism. This discovery mechanism is as simple as finding a >>> service via its name, like you want to access a maps engine by just using >>> its name. You can use DBUS in linux or Client-Server mechanism in Symbian, >>> but SFW is a cross platform solution and aims at its intended use cases. >>> >>> Thanks, >>> Srikanth >>> >>> On Sat, Jan 22, 2011 at 5:01 AM, Koichi Mori <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> I'm a bit unclear what Service Framework API is for. Is this, for >>>> instance on Linux, accessing platform services through dbus, or something >>>> else? >>>> >>>> I tried to get dubs interface from QML on Maemo5 but I never get it >>>> work. My test code looks like below, but it always complains "WARNING: No >>>> default service found for interface name: "org.bluez.Manager"" and valid >>>> property of course is false. >>>> >>>> Rectangle{ >>>> Component.onCompleted:{ >>>> console.log(btManager.valid); >>>> } >>>> Service { >>>> id: btManager >>>> interfaceName: 'org.bluez.Manager' >>>> } >>>> } >>>> >>>> -- >>>> BR, >>>> Koichi Mori >>>> >>>> _______________________________________________ >>>> Qt-mobility-feedback mailing list >>>> >>>> [email protected] >>>> http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback >>>> >>>> >>> >>> _______________________________________________ >>> Qt-mobility-feedback mailing list >>> [email protected] >>> http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback >>> >>> >> >> >> -- >> BR, >> Koichi Mori >> >> _______________________________________________ >> Qt-mobility-feedback mailing list >> [email protected] >> http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback >> >> > > _______________________________________________ > Qt-mobility-feedback mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback > > -- BR, Koichi Mori
_______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback
