DBusSharp
From NDesk
| Revision as of 21:09, 25 October 2006 (edit) Alp (Talk | contribs) ← Previous diff |
Revision as of 21:11, 25 October 2006 (edit) (undo) Alp (Talk | contribs) Next diff → |
||
| Line 20: | Line 20: | ||
| It aims for compatibility with [http://www.mono-project.com/ Mono] and Microsoft .NET frameworks | It aims for compatibility with [http://www.mono-project.com/ Mono] and Microsoft .NET frameworks | ||
| supporting the 2.0 profile. Backward compatibility with 1.0 will not be | supporting the 2.0 profile. Backward compatibility with 1.0 will not be | ||
| - | a consideration. | + | a consideration. Ongoing work to ensure CLS compliance means that managed D-Bus can be used by any language that can target the CLR. |
| <!-- | <!-- | ||
Revision as of 21:11, 25 October 2006
dbus-sharp is a C# implementation of D-Bus. It's often referred to as "managed D-Bus" to avoid confusion with existing bindings (which wrap libdbus).
D-Bus is an inter-process communication framework that lets applications interface with the system event bus as well as allowing them to talk to one another in a peer-to-peer configuration.
Contents |
Status
This software is under development but is already used by a wide range of applications for tasks as simple as maintaining a single instance of the GUI to whole instant messaging frameworks and hardware detection APIs.
It provides a tested, high-performance bridge to and from all systems that are exposed via D-Bus, regardless of programming language, UI toolkit or license.
The code is a clean-room implementation based on the D-Bus Specification Version 0.11 and study of the wire protocol of existing tools.
It aims for compatibility with Mono and Microsoft .NET frameworks supporting the 2.0 profile. Backward compatibility with 1.0 will not be a consideration. Ongoing work to ensure CLS compliance means that managed D-Bus can be used by any language that can target the CLR.
Cross platform support
Supported platforms
A standard build of managed D-Bus will work across a wide range of platforms:
- x86
- 64-bit (eg. AMD64)
- Big endian (eg. PPC)
- Mono 1.1.13 to 1.1.18 and newer
- Linux
- FreeBSD (only peer-to-peer connections tested so far)
Untested platforms
Managed D-Bus should work on these platforms but no testing has been done yet due to lack of hardware, or due to the unavailability of a libdbus port:
- FreeBSD connections to libdbus (peer credential support not yet tested)
- Mac OS X
- Solaris
- Microsoft Windows / .NET runtime
Users
Even though this software is not yet released, developers of a few applications have decided to ignore the warnings and (correctly) bundle it or depend on it directly as a moving target. This kind of arrangement can work if you're on good terms with someone who can maintain dbus-sharp, but ideally you should wait for a stable release.
- NDesk component object model (NParts etc.)
- telepathy-sharp
- Tapioca VoIP and IM application development framework (tapioca-sharp)
- Landell VoIP and IM client using Gtk#
- Banshee provides and uses a media player API, and uses Gnome Power Manager, Gnome NetworkManager, notify-sharp
- hal-sharp is provides access to HAL, the Hardware Abstraction Layer
- NotifySharp provides a client implementation for Desktop Notifications and works as a libnotify client replacement
- F-Spot personal photo management application, for single-instance detection [1]
Contact
Support can be found on the #managed-dbus IRC channel on irc.gnome.org
There is no mailing list or email contact address.
Download
0.1
Version 0.1 is out: http://www.ndesk.org/archive/dbus-sharp/
This is an emergency release to provide a working alternative for applications stuck with the unmaintained dbus-sharp binding for libdbus. The API/ABI may change in future releases, and it hasn't been audited for security, which means that it shouldn't be used to provide services to an untrusted audience over TCP. However, a number of applications are successfully using this code base already. Event handlers must be manually removed (foo.MyEvent -= HandleMyEvent;) to avoid flooding the daemon with match rules. MarshalByRefObject may not be supported in future releases, so you should stick to using interfaces to define dbus API. Exceptions are not consistently mapped but should work both in exported and imported API.
Development
See the development roadmap for a detailed list of remaining tasks.
git-clone git://git.ndesk.org/pub/scm/dbus-sharp
The dbus-sharp API is not stable. In particular, please don't check this into your cvs/svn repository or bundle it with your program. And don't even think about installing it in the user's GAC or packaging it for your distribution yet.
There is also a module which provides GLib integration as an optional extra: