Development/Tutorials/D-Bus/Introduction - Revision history

AnneW at 12:35, 13 July 2012

2012-07-13T12:35:40Z

Neverendingo: Text replace - "" to ""

2011-06-29T20:51:07Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:44:51Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:44, 29 June 2011
			
Line 82:
Line 82:
  A D-Bus message contains an address made up of all the above components so that it can be routed to the correct application, object and method call. Such an address might look like this:   A D-Bus message contains an address made up of all the above components so that it can be routed to the correct application, object and method call. Such an address might look like this:
    
− <code> + <syntaxhighlight lang="text">
  org.kde.krunner /ScreenSaver org.kde.screensaver.setBlankOnly   org.kde.krunner /ScreenSaver org.kde.screensaver.setBlankOnly
  </code>   </code>
Line 88:
Line 88:
  In this case <tt>org.kde.krunner</tt> is the service, <tt>/ScreenSaver</tt> is the path to the object, <tt>org.kde.screensaver</tt> is the interface the object exports and <tt>setBlankOnly</tt> is a method in the interface. If the <tt>/ScreenSaver</tt> object only provides the <tt>org.kde.screensaver</tt> interface (or the <tt>setBlankOnly</tt> method is unique amongst the services it implements) then this would work equally well as an address:   In this case <tt>org.kde.krunner</tt> is the service, <tt>/ScreenSaver</tt> is the path to the object, <tt>org.kde.screensaver</tt> is the interface the object exports and <tt>setBlankOnly</tt> is a method in the interface. If the <tt>/ScreenSaver</tt> object only provides the <tt>org.kde.screensaver</tt> interface (or the <tt>setBlankOnly</tt> method is unique amongst the services it implements) then this would work equally well as an address:
    
− <code> + <syntaxhighlight lang="text">
  org.kde.krunner /ScreenSaver setBlankOnly   org.kde.krunner /ScreenSaver setBlankOnly
  </code>   </code>



Rakuco: /* Services */ Make the first paragraph easier to understand
2009-08-16T23:01:54Z
‎Services:  Make the first paragraph easier to understand

				
				
				
				
			
			← Older revision
			Revision as of 23:01, 16 August 2009
			
Line 62:
Line 62:
  A '''service''' represents an application connection to a bus.   A '''service''' represents an application connection to a bus.
    
− '''Service''' here corresponds to "well-known" [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology. A term "Bus name" is a bit confusing. Regardless of how it sounds like, '''Bus names''' are the names of connections(!) on the bus, not names of buses(!). So here the term '''service''' used, as Qt Documentation calls it. + '''Service''' here corresponds to "well-known" [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology. The term "Bus name" is a bit confusing. Regardless of how it sounds like, '''Bus names''' are the names of connections(!) on the bus, not names of buses(!). So here the term '''service''' will be used, as the Qt Documentation calls it.
    
  These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.   These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.



Rakuco: /* Services */ Fix capitalization typo
2009-08-16T22:57:47Z
‎Services:  Fix capitalization typo

				
				
				
				
			
			← Older revision
			Revision as of 22:57, 16 August 2009
			
Line 62:
Line 62:
  A '''service''' represents an application connection to a bus.   A '''service''' represents an application connection to a bus.
    
− '''service''' here corresponds to "well-known" [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology. A term "Bus name" is a bit confusing. Regardless of how it sounds like, '''Bus names''' are the names of connections(!) on the bus, not names of buses(!). So here the term '''service''' used, as Qt Documentation calls it. + '''Service''' here corresponds to "well-known" [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology. A term "Bus name" is a bit confusing. Regardless of how it sounds like, '''Bus names''' are the names of connections(!) on the bus, not names of buses(!). So here the term '''service''' used, as Qt Documentation calls it.
    
  These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.   These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.



Sreich: /* Services */ QT==Apples junk Qt==the awesome toolkit
2009-04-24T00:06:24Z
‎Services:  QT==Apples junk Qt==the awesome toolkit

				
				
				
				
			
			← Older revision
			Revision as of 00:06, 24 April 2009
			
Line 62:
Line 62:
  A '''service''' represents an application connection to a bus.   A '''service''' represents an application connection to a bus.
    
− '''service''' here corresponds to "well-known" [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology. A term "Bus name" is a bit confusing. Regardless of how it sounds like, '''Bus names''' are the names of connections(!) on the bus, not names of buses(!). So here the term '''service''' used, as QT Documentation calls it. + '''service''' here corresponds to "well-known" [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology. A term "Bus name" is a bit confusing. Regardless of how it sounds like, '''Bus names''' are the names of connections(!) on the bus, not names of buses(!). So here the term '''service''' used, as Qt Documentation calls it.
    
  These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.   These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.



Tampakrap: clarifying what Bus names are, and from where term ''service'' came.
2009-03-01T20:00:09Z
clarifying what Bus names are, and from where term ''service'' came.

				
				
				
				
			
			← Older revision
			Revision as of 20:00, 1 March 2009
			
Line 60:
Line 60:
  === Services ===   === Services ===
    
− ('''service''' here corresponds to so-called well-known [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology) + A '''service''' represents an application connection to a bus.
    
− A '''service''' represents an application connection to a bus. These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus. + '''service''' here corresponds to "well-known" [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology. A term "Bus name" is a bit confusing. Regardless of how it sounds like, '''Bus names''' are the names of connections(!) on the bus, not names of buses(!). So here the term '''service''' used, as QT Documentation calls it.
  +  
  + These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.
    
  You should use the domain name for your organization or application for your service names. For example if your domain is <tt>awesomeapps.org</tt> and the name of your application is <tt>wickedwidget</tt> you would probably use <tt>org.awesomeapps.wickedwidget</tt> as the service name on the bus.   You should use the domain name for your organization or application for your service names. For example if your domain is <tt>awesomeapps.org</tt> and the name of your application is <tt>wickedwidget</tt> you would probably use <tt>org.awesomeapps.wickedwidget</tt> as the service name on the bus.



Tampakrap: clarified connection between services and bus names
2009-03-01T19:21:42Z
clarified connection between services and bus names

				
				
				
				
			
			← Older revision
			Revision as of 19:21, 1 March 2009
			
Line 59:
Line 59:
    
  === Services ===   === Services ===
  + 
  + ('''service''' here corresponds to so-called well-known [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology)
    
  A '''service''' represents an application connection to a bus. These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.   A '''service''' represents an application connection to a bus. These are kept unique by using a "reverse domain name"  approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.



Tampakrap: Added language navgiation
2008-07-27T14:15:09Z
Added language navgiation

				
				
				
				
			
			← Older revision
			Revision as of 14:15, 27 July 2008
			
Line 1:
Line 1:
  + {{Template:I18n/Language Navigation Bar|Development/Tutorials/D-Bus/Introduction}}
  + 
  {{TutorialBrowser|   {{TutorialBrowser|
    



Amoskahiga: /* Signals */
2007-12-05T17:08:44Z
‎Signals

				
				
				
				
			
			← Older revision
			Revision as of 17:08, 5 December 2007
			
Line 100:
Line 100:
  === Signals ===   === Signals ===
    
− Signals are like method calls except that they happen in the "reverse" direction and are not tied to a single destination. A signal is emitted by the application which is exporting the interface and is available to any application on the same bus. This allows an application to spontaneously advertise changes in state or other events to any applications which may be interested in tracking those changes. + Signals are like method calls except that they happen in the "reverse" direction and are not tied to a single destination. A signal is emitted by the application which is exporting the interface and is available to any application on the same bus. This allows an application to spontaneously advertise changes in state or other events, to any applications which may be interested in tracking those changes.
    
  If this sounds a lot like the signal and slots mechanism in Qt, that's because it is. For all intents and purposes it is a non-local version of the same functionality.   If this sounds a lot like the signal and slots mechanism in Qt, that's because it is. For all intents and purposes it is a non-local version of the same functionality.

← Older revision		Revision as of 12:35, 13 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Development/Tutorials/D-Bus/Introduction}}~~

	{{TutorialBrowser\|		{{TutorialBrowser\|

← Older revision		Revision as of 19:21, 1 March 2009
Line 59:		Line 59:

	=== Services ===		=== Services ===
		+
		+	('''service''' here corresponds to so-called well-known [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names Bus names] in the D-Bus specification terminology)

	A '''service''' represents an application connection to a bus. These are kept unique by using a "reverse domain name" approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.		A '''service''' represents an application connection to a bus. These are kept unique by using a "reverse domain name" approach, as can be seen in many other systems that need to namespace for multiple components. Most services provided by applications from the KDE project itself use the <tt>org.kde</tt> prefix to their service name. So one may find "org.kde.screensaver" advertised on the session bus.

← Older revision		Revision as of 14:15, 27 July 2008
Line 1:		Line 1:
		+	{{Template:I18n/Language Navigation Bar\|Development/Tutorials/D-Bus/Introduction}}
		+
	{{TutorialBrowser\|		{{TutorialBrowser\|