grep FIXME in dbus-auth.c
pending | the pending call we block for a reply on |
FIXME what if we call out to application code to handle a message, holding the dispatch lock, and the application code runs the main loop and dispatches again? Probably deadlocks at the moment.
error | the error. |
error | the error. |
dir | the directory name | |
next_component | the filename |
str | the string to read from | |
pos | position to read from | |
element_type | type of array elements | |
value | place to return the array | |
n_elements | number of array elements to read | |
byte_order | the byte order, used to read the array length | |
new_pos | NULL or location to store a position after the elements |
str | the string | |
start | first byte index to check | |
len | number of bytes to check |
require that dict entries are in an array
type_str | the string | |
type_pos | where the typecodes start | |
len | length of typecodes |
data | the data | |
len | the length of the data | |
offset | where to start counting for byte indexes |
If this fails due to lack of memory, the message is hosed and you have to start over building the whole message.
message | the message | |
error | error to be filled in on failure | |
first_arg_type | the first argument type | |
.</dd></dl> |
message | the message | |
path | place to store allocated array of path components; NULL set here if no path field exists |
tree | the global object tree | |
message | the message to dispatch |
pending | the pending call |
Need notification to apps of disconnection, may matter for some transports
a | first string | |
b | second string |
memcmp is probably faster
a | first string | |
a_start | where to start substring in first string | |
a_len | length of substring in first string | |
b | second string | |
b_start | where to start substring in second string |