diff options
| author | Havoc Pennington <hp@redhat.com> | 2003-09-21 19:53:56 +0000 |
|---|---|---|
| committer | Havoc Pennington <hp@redhat.com> | 2003-09-21 19:53:56 +0000 |
| commit | a683a80c409cc4f2e57ba6a3e60d52f91b8657d0 (patch) | |
| tree | 739f2f5f583c987a64b92d007062ae8a6ea9b161 /doc | |
| parent | daf8d6579e1ae0ea748810b63180bd5eea2ab9c4 (diff) | |
2003-09-21 Havoc Pennington <hp@pobox.com>
Get matching rules mostly working in the bus; only actually
parsing the rule text remains. However, the client side of
"signal connections" hasn't been started, this patch is only the
bus side.
* dbus/dispatch.c: fix for the matching rules changes
* bus/driver.c (bus_driver_handle_remove_match)
(bus_driver_handle_add_match): send an ack reply from these
method calls
* glib/dbus-gproxy.c (dbus_gproxy_begin_call): fix order of
arguments, reported by Seth Nickell
* bus/config-parser.c (append_rule_from_element): support
eavesdrop=true|false attribute on policies so match rules
can be prevented from snooping on the system bus.
* bus/dbus-daemon-1.1.in: consistently use terminology "sender"
and "destination" in attribute names; fix some docs bugs;
add eavesdrop=true|false attribute
* bus/driver.c (bus_driver_handle_add_match)
(bus_driver_handle_remove_match): handle AddMatch, RemoveMatch
messages
* dbus/dbus-protocol.h (DBUS_SERVICE_ORG_FREEDESKTOP_BROADCAST): get
rid of broadcast service concept, signals are just always broadcast
* bus/signals.c, bus/dispatch.c, bus/connection.c, bus/bus.c:
mostly implement matching rules stuff (currently only exposed as signal
connections)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/TODO | 9 |
1 files changed, 6 insertions, 3 deletions
@@ -80,12 +80,15 @@ - the invalid messages in the test suite are all useless because they are invalid for the wrong reasons due to protocol changes - - Nuke the org.freedesktop.Broadcast service; instead, - just broadcast messages of type signal - - I don't want to introduce DBusObject, but refcounting and object data could still be factored out into an internal "base class" perhaps. + - modify the auth protocol to also support other initial-handshake + type of information + + - document the auth protocol as a set of states and transitions, and + then reimplement it in those terms + - Header fields names are required to be aligned on a 4 byte boundary at the moment. No alignment should be neccessary. |