DBusSharp/Releases
From NDesk
Contents |
[edit] 2007-03-12
This is a stable release with backported fixes. See dbus-sharp-0.4.y for patch details. All users are advised to upgrade, as previous releases depend on buggy Mono behaviour that was recently fixed and may cease to function correctly.
Important patches:
- Avoid recursing interfaces: Prevents handlers from being hooked up twice in certain corner cases and fixes introspection output in those same cases
- Workaround for Mono bug #81035 (memory leak)
- Workaround for old Mono: Don't use SortedDictionary: This fixes the build with older Mono releases
- Various minor correctness fixes to make sure this will build and work well on newer Mono releases when they become available
[edit] 2007-03-07
This release enables faster compiled write marshalers and a workaround for a small memory leak in Mono bug #81035. Applications bunding managed D-Bus need not upgrade to this release. There will shortly be a 0.4 series release with the most important changes backported.
0.5 also features Makefile and code fixes for MS .NET. There is still one issue that prevents it from working out of the box due to CAS security. This issue will be addressed in soon.
[edit] 2007-02-20
New source files: MatchRule.cs
Fixes:
- Exported properties now work (they could only be imported before). Note that this has nothing to do with the org.freedesktop.DBus.Properties interface.
- Objects can now be unregistered. Unregister was before just a no-op.
- Compiled proxy methods/marshalers for incoming signals are now cached, so registering many objects of the same type should not leak or have much overhead.
- Optimization for incoming byte arrays.
- More robust match rule logic.
The unregistration support and working exported properties makes this the first feature-complete release.
There is no urgent need to upgrade 0.4 bundled with applications unless you need the new features.
[edit] 2007-02-05
"make install" does not yet work out of the box, but assemblies are strongly named. Distributors may optionally ship this package if they complete the installation manually. Bundling is still recommended with this release.
Both APIs are both cleaned up to only expose API that is meant to be public.
Notable dbus-sharp fixes include a fix that makes event exporting through interfaces work (noticed by the Muine team). Methods can now be overloaded in both imported and exported interfaces based on parameters, and method selection on multiple exported interfaces by a single object is improved. This fix also provides a slight performance boost.
dbus-sharp-glib was fixed to avoid a spontaneous exception when the bus is unexpectedly disconnected.
If you are bundling the code, you should not use ndesk.snk or define STRONG_NAME.
For your exported D-Bus service to be properly activatable, you should register objects _before_ requesting names or making any other calls. To make sure your program can be activated, make sure it's not running and that the service file is installed. Then run this, substituting $bus_name to your service's name eg. org.gnome.Banshee:
dbus-send --print-reply=literal --dest=$bus_name / org.freedesktop.DBus.Introspectable.Introspect
The program should start, and the introspection data should contain a dump of the main application object rather than an empty node tag.
[edit] 0.3.1
FreeBSD support introduced in 0.3 broke 64-bit Linux. This point-release provides a fix.
It also provides minor cleanups and the ability to parse more complex object trees as variants.
Notes to integrators:
- The DType enumeration will soon become internal although it is not changed in this release. Please remove use of this enum in your code or make your own copy. Keep in mind that's there's no sensible reason for applications to use DType or something similar because other message parsing machinery in managed D-Bus is not public, and that D-Bus has a recursive type system, so the enum should have been called DToken or similar anyway.
- Remember to run your application with DBUS_VERBOSE=1 when testing. Some of the warnings may indicate serious bugs in your interfaces, particularly the "expected signature mismatch" warning. Some of these warnings will become hard exceptions in future releases, while others are usually harmless (such as the missing handler warnings). If in doubt, ask on the IRC channel.
[edit] 0.3
Notes to integrators:
- API change: The NameReply enum is now RequestNameReply
- New files: UnixTransport.cs, SocketTransport.cs should be included when bundling the code
- As always, UnixMonoTransport.cs and IntrospectionSchemas.cs should not be included unless you have specific needs
- If you use dbus-sharp-glib, you must upgrade to the latest release
- the -unsafe gmcs/csc compiler flag has been required since 0.2
[edit] 0.2
Support was added for reading non-native endian messages. ObjectPaths and Signatures were made more robust and several exception messages were improved. A complete list of changes is available in the version control system. There have been no changes in the high-level or the low-level public API in this release. dbus-sharp-glib remains stable at version 0.1.
[edit] 0.1
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.