summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Prepare 1.5.0dbus-1.5.0Simon McVittie2011-04-113-7/+22
| | | | | - D-Bus Specification 0.16 - libtool 9:0:6
* Merge branch 'dbus-1.4'Simon McVittie2011-04-084-24/+40
|\ | | | | | | | | Conflicts: NEWS
| * development versionSimon McVittie2011-04-082-1/+6
| |
| * Prepare version 1.4.8dbus-1.4.8Simon McVittie2011-04-082-3/+13
| |
| * activation: Strip out code to compare by Exec=Colin Walters2011-04-081-18/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit: 075945f6 (John (J5) Palmieri 2005-07-14 20:44:15 +0000 some code was added to compare services by Exec key. The changelog is not pariticularly informative as to why this was added. But while debugging other code, we noticed this. Comparing by Exec key is not in the specification, and triggered a problem where while converting services to use systemd for activation, a change was made to use Exec=/bin/false and simply rely on systemd to activate. While I think it was broken for the service files to be changed to Exec=/bin/false, we shouldn't be doing something here that's not in the spec either. Reviewed-by: Will Thompson <will.thompson@collabora.co.uk> Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=35750
| * oops, fix XML mis-nestingSimon McVittie2011-04-071-0/+1
| |
| * list which parts of the Desktop Entry spec apply to service filesSven Herzberg2011-04-071-3/+22
| | | | | | | | | | Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=19159
* | Merge branch 'arg0namespace-24317'Simon McVittie2011-04-076-71/+627
|\ \ | | | | | | | | | | | | | | | | | | Reviewed-by: David Zeuthen <davidz@redhat.com> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=24317 Bug: https://bugs.freedesktop.org/show_bug.cgi?id=31818 Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34870
| * | Mention dbus-specification.xml's separate versioning in HACKINGSimon McVittie2011-04-071-1/+6
| | |
| * | Check parsing (or otherwise) of path_namespace in match rulesSimon McVittie2011-04-071-0/+18
| | |
| * | Remove support for trailing "." on arg0namespaceSimon McVittie2011-04-072-64/+11
| | |
| * | Rename path_prefix to path_namespace and disallow trailing '/'Simon McVittie2011-04-073-119/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | Also disallow having both path and path_namespace in the same match rule (it wouldn't make sense, path is more specific than path_namespace). As per IRC discussion with davidz and wjt. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34870
| * | Document when arg0namespace was added, for completenessSimon McVittie2011-04-071-0/+7
| | |
| * | Document when argNpath was added, for completenessSimon McVittie2011-04-071-0/+9
| | |
| * | specification: fix versioningSimon McVittie2011-04-071-4/+4
| | | | | | | | | | | | We've added things since 0.15, so this isn't still 0.15.
| * | path_prefix: anchor matches at path-component boundaries, and give examplesSimon McVittie2011-04-072-5/+40
| | | | | | | | | | | | | | | It seems wrong that path_prefix="/foo" matches /foobar, and it isn't difficult or expensive to check.
| * | Add path_prefix match ruleDavid Zeuthen2011-04-073-1/+192
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a new path_prefix match rule that can be used for efficient implementations of the org.freedesktop.DBus.ObjectManager interface (see bug 34869). https://bugs.freedesktop.org/show_bug.cgi?id=34870 Signed-off-by: David Zeuthen <davidz@redhat.com>
| * | re-word description of arg0namespaceSimon McVittie2011-04-071-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's unclear at first reading whether "may contain only one element" means "elements >= 1, as an exception to the usual rule that elements >= 2" (which is what was intended), or "elements == 1". "Like a bus name or interface name" is a little ambiguous because they have different syntactic restrictions: specifically allow any valid bus name, which also allows all interface names.
| * | signals.h: rename argument in declaration to match implementationSimon McVittie2011-04-071-1/+1
| | |
| * | Merge remote-tracking branch 'wjt/arg0namespace' into arg0namespace-24317Simon McVittie2011-04-075-53/+448
| |\ \
| | * | Define arg0namespace in the specificationWill Thompson2010-11-231-0/+32
| | | |
| | * | Validate arg0namespace matches' values.Will Thompson2010-11-233-18/+119
| | | | | | | | | | | | | | | | | | | | I could be convinced that this is overkill, but it seems sensible to forbid obviously-broken arg0namespace matches.
| | * | Supporting matching argument 0 as a namespaceWill Thompson2010-11-232-18/+154
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rather like "arg0path='/foo/'" matching all object paths starting with "/foo/", this adds support for matching a prefix of a string argument with "arg0namespace='org.freedesktop.Telepathy.Client.'" (for example). This is mostly intended for use with NameOwnerChanged and PropertiesChanged; thus, only matching the 0th argument is permitted. (This also means it could work with the multicast-plus-socket-filters model being considered for DBus-in-the-kernel without having to hash every period-separated prefix of every string argument.)
| | * | Explicitly specify which types argX and argXpath matchWill Thompson2010-11-231-4/+5
| | | |
| | * | Support matching path arguments with argXpathWill Thompson2010-11-211-10/+24
| | | | | | | | | | | | | | | | | | | | The existing implementation only matched arguments of type 's', not of type 'o'!
| | * | Add test cases for argXpath matchingWill Thompson2010-11-211-3/+102
| | | |
| | * | Document the rationale for argXpath matching.Will Thompson2010-11-211-10/+22
| | | |
* | | | Merge branch 'dbus-1.4'Simon McVittie2011-04-072-94/+90
|\ \ \ \ | |/ / / |/| | / | | |/ | |/|
| * | Break up the monster conditional in config-parser so gcov can copeSimon McVittie2011-04-072-94/+90
| | | | | | | | | | | | | | | Bug: https://bugs.freedesktop.org/show_bug.cgi?id=10887 Reviewed-by: Colin Walters <walters@verbum.org>
* | | Update NEWS for masterSimon McVittie2011-03-141-0/+6
| | |
* | | Merge branch 'dbus-1.4'Simon McVittie2011-03-141-0/+4
|\ \ \ | |/ /
| * | Update NEWSSimon McVittie2011-03-141-0/+4
| | |
* | | Merge branch 'dbus-1.4', rejecting all changesSimon McVittie2011-03-140-0/+0
|\ \ \ | |/ / | | | | | | | | | This commit changes nothing, but means that merge tracking won't try to apply the reversion of d1d395774435..09c9d6406b75f to master in future.
| * | Revert merge of master (dbus-1.5) into dbus-1.4Simon McVittie2011-03-1413-304/+167
| | | | | | | | | | | | | | | This reverts commits d1d395774435..09c9d6406b75f, keeping Lennart's addition of UnknownInterface etc.
* | | connection: hook UnknownObject and UnknownInterface up where appropriateLennart Poettering2011-03-114-6/+16
|/ / | | | | | | | | | | | | | | This makes use of UnknownInterface and UnknownObject where appropriate in the D-Bus core. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34527 Reviewed-By: Simon McVittie <simon.mcvittie@collabora.co.uk>
* | protocol: introduce four new errorsLennart Poettering2011-03-101-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | UnknownInterface, UnknownObject, UnknownProperty and PropertyReadOnly, as discussed on the ML. The first two are already used by various bindings, such as the Qt and Java binding, but have never been made official. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34527 Reviewed-by: David Zeuthen <davidz@redhat.com> Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
* | Make dbus_type_is_valid into public APISimon McVittie2011-03-108-50/+57
| | | | | | | | | | | | | | | | | | | | This is just as useful for bindings as dbus_signature_validate, and I think it's a good design principle to say that anything checked in a _dbus_return_if_fail should be something the caller could check for themselves. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=20496 Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
* | Merge branch 'dbus-1.4'Simon McVittie2011-03-107-13/+71
|\ \
| * | add doxygen.stamp to .gitignoreSimon McVittie2011-03-101-0/+1
| | | | | | | | | | | | | | | Bug: https://bugs.freedesktop.org/show_bug.cgi?id=35182 Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
| * | _dbus_marshal_write_fixed_multi: remove obsolete FIXME commentSimon McVittie2011-03-101-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As far as I can tell, we've never accepted out-of-range booleans and canonicalized them, ever since this was first committed in 2004. If sent, they'd be considered to be invalid by recipients, so they're unambiguously an error. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=35182 Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
| * | dbus_message_iter_append_basic: remove misleading documentationSimon McVittie2011-03-101-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | This function specifically doesn't support Unix fds and is documented as such. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=35182 Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
| * | Implement uninstallation and cleanup for Doxygen docs, fixing distcheckSimon McVittie2011-03-101-0/+8
| | | | | | | | | | | | Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
| * | Merge branch 'validate-when-sending-16338' into dbus-1.4Simon McVittie2011-03-103-0/+52
| |\ \ | | | | | | | | | | | | Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
| | * | dbus_message_iter_append_fixed_array: add a check for valid booleansSimon McVittie2011-03-041-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The reasoning is the same as for dbus_message_iter_append_basic. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=16338 Reviewed-by: Cosimo Alfarano <cosimo.alfarano@collabora.co.uk>
| | * | dbus_message_iter_append_basic: validate booleans tooSimon McVittie2011-03-041-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sending, for instance, ((dbus_bool_t) 666) is a programming error and should be diagnosed as such. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=16338 Reviewed-by: Cosimo Alfarano <cosimo.alfarano@collabora.co.uk>
| | * | dbus_message_iter_append_basic: check string-like arguments for validitySimon McVittie2011-03-043-0/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Strings: UTF-8 with no embedded NULs, by adding a new internal function, _dbus_check_is_valid_utf8 Object paths, signatures: the obvious syntactic checks This moves some of the burden of validation to the sender. When sending <http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt> 10240 times with up to 1024 parallel calls pending, on a single-core ARM Linux device, I found that user CPU time in dbus-spam increased by up to 80% as a result of the validation. However, when sending messages to dbus-daemon, overall throughput only reduced by 15%, and when sending messages to an echo service, overall throughput actually improved by around 14% (presumably because making the sender CPU-bound influenced kernel scheduling). Bug: https://bugs.freedesktop.org/show_bug.cgi?id=16338 Bug-NB: NB#223152 Reviewed-by: Cosimo Alfarano <cosimo.alfarano@collabora.co.uk>
| * | | dbus_type_is_basic etc.: it is an error to pass in bad typecodesSimon McVittie2011-03-101-7/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, the comments said "this function will crash", but that's not strictly true (checks can be disabled or made non-fatal). Their behaviour is undefined if you do that, though. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=20496 Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
* | | | Require specific user action to compile without 64-bit supportSimon McVittie2011-03-101-4/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The D-Bus type system isn't implementable without 64-bit support, although for historical reasons we have some sort of semi-working support for platforms with no 64-bit integers. Let's find out whether any practically relevant platform still lacks these types... (GLib appears to have required 64-bit integer types since 2001.) Bug: https://bugs.freedesktop.org/show_bug.cgi?id=35114 Reviewed-by: Lennart Poettering <lennart@poettering.net>
* | | | Merge branch 'dbus-1.4'Simon McVittie2011-03-101-1/+1
|\ \ \ \ | |/ / /
| * | | autogen: add -I m4 to aclocal pathLennart Poettering2011-03-101-1/+1
| | | | | | | | | | | | | | | | | | | | This fixes 2b5959882a403cddba754b37b58bdc49bff01f90 which forgot to add m4/ to the command line of aclocal but moved scripts there.
View Lorry Controller Status