• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

examples/H03-May-2022-693517

src/H03-May-2022-6,0964,108

tools/H03-May-2022-430343

AUTHORSH A D12-Jan-200827 21

COPYINGH A D12-Jan-20081 KiB2117

INSTALLH A D13-Jan-20089.2 KiB235177

Makefile.amH A D12-Jan-2008323 2317

Makefile.inH A D03-May-202219.6 KiB632553

READMEH A D12-Jan-20081.4 KiB3827

aclocal.m4H A D13-Jan-200821.7 KiB613542

config.guessH A D13-Jan-200843.5 KiB1,5171,305

config.subH A D13-Jan-200831.9 KiB1,6231,479

configureH A D13-Jan-2008100.8 KiB3,6132,857

configure.acH A D13-Jan-20081.2 KiB6247

install-shH A D13-Jan-200812.9 KiB508340

missingH A D13-Jan-200810.9 KiB368275

ndesk-dbus-1.0.pc.inH A D12-Jan-2008340 1210

README

1D-Bus for .NET
2==============
3
4This is a C# implementation of D-Bus. It's often referred to as "managed
5D-Bus" to avoid confusion with existing bindings (which wrap libdbus).
6
7See http://www.ndesk.org/DBusSharp
8
9D-Bus is an inter-process communication framework that lets applications
10interface with the system event bus as well as allowing them to talk to
11one another in a peer-to-peer configuration.
12
13See http://www.freedesktop.org/wiki/Software/dbus for general
14information on the D-Bus IPC mechanism.
15
16This software is under active development but is already used by a wide
17range of applications for tasks as simple as maintaining a single
18instance of the GUI to whole instant messaging frameworks and hardware
19detection APIs.
20
21It provides a tested, high-performance bridge to and from all systems
22that are exposed via D-Bus, regardless of programming language, UI
23toolkit or license. The source code is MIT X11 licensed (Free
24Software/Open Source), allowing integration into other projects with
25very few restrictions.
26
27The code was written and is maintained by Alp Toker <alp@atoker.com>
28
29It is a clean-room implementation based on the D-Bus Specification
30Version 0.11 and study of the wire protocol of existing tools.
31
32It aims for compatibility with Mono and Microsoft .NET frameworks
33supporting the 2.0 profile. Backward compatibility with 1.0 will not be
34a consideration.
35
36--
37Alp Toker <alp@atoker.com>
38