summaryrefslogtreecommitdiff
path: root/src/search-channel.c
Commit message (Collapse)AuthorAgeFilesLines
* Use non-deprecated GValueArray functionsSimon McVittie2013-11-041-18/+5
| | | | | | | | This works around GValueArray being deprecated in GLib, but still part of dbus-glib-derived APIs. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=26609 Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
* Don't use add_child_with_content with NULL/"" contentWill Thompson2012-11-271-3/+3
| | | | | This is harmless, but looks messy. It's leftover clutter from the loudmouth era.
* Avoid manually setting WockyNode.ns where sensible.Will Thompson2012-11-271-2/+2
| | | | There's still one case in the Jingle code which seems justifiable.
* Stop accessing sealed tp-glib structsXavier Claessens2012-09-111-5/+0
|
* Use meta-headers for everythingSimon McVittie2012-05-301-5/+2
| | | | | Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=49384
* Use TP_ERROR instead of deprecated TP_ERRORSSimon McVittie2012-05-071-13/+13
| | | | | Bug: https://bugs.freedesktop.org/show_bug.cgi?id=49596 Reviewed-by: Xavier Claessens <xavier.claessens@collabora.co.uk>
* Update Wocky snapshot for One Big Header.Will Thompson2012-02-061-1/+1
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=27489
* search: move to WockyNodeIterWill Thompson2012-01-311-38/+30
| | | | | In one place, I actually replaced a confusing use of NodeIter with wocky_node_get_content_from_child(). I think the result is much clearer.
* search-channel: stop using lm_message_node_get_child_with_namespaceWill Thompson2012-01-311-4/+4
| | | | In all cases, we wanted a direct child.
* Remove vestigial Loudmouth headers and build systemWill Thompson2012-01-271-1/+0
|
* Remove LmHandlerResultWill Thompson2012-01-271-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | The callback type for _gabble_connection_send_with_reply returned one of these. All instances, bar two, returned LM_HANDLER_RESULT_REMOVE_MESSAGE, which makes sense, because if you send an IQ you had better be prepared to handle the reply. When I removed lm_connection_send_with_reply(), I stopped _gabble_connection_send_with_reply() paying attention to the return value, with no apparent ill effects. The two which returned LM_HANDLER_RESULT_ALLOW_MORE_HANDLERS were: • the disco pipeline's reply handler, in the case where the request is no longer in the pipeline (such as in a timeout). I checked, and as far as I can tell nothing is trying to scrape any information out of zombie disco replies. • the request pipeline's reply handler, in the same case. I couldn't be bothered to check for this, but I don't think it will pose any ill effects because normally the handler is the highest-priority callback, so anyone trying to catch these would not catch the ones which were not cancelled… which seems unlikely.
* Delete LmMessage{,Type,SubType} typedefsWill Thompson2012-01-271-6/+6
|
* Remove lm_message_new[_with_subtype]Will Thompson2012-01-271-11/+9
|
* Expunge lm_message_ref and lm_message_unref.Will Thompson2012-01-261-2/+2
| | | | And also a couple of uses of lm_message_get_node().
* Merge branch 'master' into BYE-BYE-LOUDMOUTHWill Thompson2012-01-261-7/+7
|\ | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: src/connection.c src/connection.h src/ft-manager.c src/jingle-content.c src/jingle-factory.c src/jingle-session.c src/message-util.c src/muc-channel.c src/muc-channel.h
| * Use _unref instead of _free _destroy when possible.unrefXavier Claessens2011-11-161-7/+7
| | | | | | | | | | | | | | | | | | | | | | Replace g_(ptr_)array_free (foo, TRUE) and g_hash_table_destroy with respectively g_(ptr_)array_unref (foo) and g_hash_table_unref. I used this command to generate this patch: for f in `find -name "*.c"`; do sed -i $f -re 's/g_ptr_array_free \(([^ ,]+), TRUE\)/g_ptr_array_unref \(\1\)/'; done See Danielle's blog for explanation of possible bug _free can do: http://blogs.gnome.org/danni/2011/11/16/mistakes-with-g_value_set_boxed/
* | Remove GabbleXmppError.Will Thompson2011-05-031-36/+7
| | | | | | | | There is a FIXME buried in here … but the tests pass.
* | stop using LmMessageNode wrapperJonny Lamb2011-05-021-56/+53
|/ | | | | | WockyNode is the future. Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
* Search: clarify handling field request resultWill Thompson2010-10-081-4/+6
| | | | | | | | Coverity got upset that we might be passing a NULL query_node to parse_search_field_response(). Actually, we never do, but rearranging the code a bit makes this more explicit. Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
* Move to undrafted ContactSearch interfaceWill Thompson2010-09-071-72/+49
|
* Use tp_base_channel_close() for search and tls channelsWill Thompson2010-08-251-17/+4
| | | | | These are the only two TpBaseChannel-based channel types which had their own exported close function which behaves exactly as the vfunc does.
* Port GabbleSearchChannel to TpBaseChannelWill Thompson2010-08-241-102/+66
|
* GabbleSearchChannel: change_search_state: use tp_error_get_dbus_nameSimon McVittie2010-07-281-16/+3
| | | | This has been available since telepathy-glib 0.7.31.
* Use telepathy-glib's code for ContactInfoSimon McVittie2010-06-081-1/+2
| | | | | | | | We already depend on the required version, 0.11.3. Some types from ContactInfo are used in ContactSearch, and need to be converted into <tp:external-type>. Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
* Search: Correctly handle replies lacking <x/>Will Thompson2010-05-031-22/+23
|
* Turn some BaseChannel properties into class propertiesWill Thompson2010-04-271-3/+5
|
* Rename to WockyStanza, WockyNode and related changesSjoerd Simons2010-04-201-6/+8
|
* the semantic of first and last has been clearedGuillaume Desmottes2009-08-261-6/+4
|
* parse_data_form: ensure to not add twice the name search keyGuillaume Desmottes2009-08-251-3/+26
|
* parse_data_form: remove found_form_type_search as we don't use itGuillaume Desmottes2009-08-251-2/+0
|
* add_search_result: no need to init the handle to 0 any moreGuillaume Desmottes2009-08-241-1/+1
|
* add gabble_search_channel_is_ready()Guillaume Desmottes2009-08-241-0/+11
|
* add gabble_search_channel_close as a public methodGuillaume Desmottes2009-08-241-5/+11
|
* gabble_search_channel_init: use g_boxed_freeGuillaume Desmottes2009-08-241-5/+1
|
* extended search results contain a title nodeGuillaume Desmottes2009-08-191-2/+4
|
* parse_extended_search_results: ignore <reported> node and fix debug message ↵Guillaume Desmottes2009-08-191-4/+4
| | | | if we hit an unknown node
* gabble_search_channel_finalize: free available_search_keysGuillaume Desmottes2009-08-191-0/+2
|
* search-channel: SearchResultReceived now returns a dict containing all the ↵Guillaume Desmottes2009-08-191-20/+31
| | | | results
* search-channel: implement openfire searchGuillaume Desmottes2009-08-191-4/+38
|
* store only supported fields in tp_to_xmpp so we can map to the right oneGuillaume Desmottes2009-08-191-21/+36
|
* emit_search_result: use the xmpp_to_tp hash table instead of hard coding fieldsGuillaume Desmottes2009-08-191-32/+37
| | | | | This had the side effect to to expose the "x-n-family" and "x-n-given" info field in the search result which is probably what we want.
* "given", "family" and "nickname" seem to be validate field for dataform ↵Guillaume Desmottes2009-08-191-0/+3
| | | | | | | searches. This unfortunally break existing test as Gabble will use these fields even if the server supports the other ones.
* Add a FIXME about unclear first/last mappingGuillaume Desmottes2009-08-191-0/+7
|
* do_search: search request are actually 'set' IQ'sGuillaume Desmottes2009-08-191-1/+1
|
* 'x' node should contain a type attribute when sending search requestGuillaume Desmottes2009-08-191-1/+4
|
* search-channel.c: support dataform searchesGuillaume Desmottes2009-08-191-20/+250
|
* emit_search_result: display the keys that have been ignoredGuillaume Desmottes2009-08-191-1/+10
|
* emit_search_result: initialize the handle to 0Guillaume Desmottes2009-08-191-1/+1
|
* parse_unextended_field_response: have to use unextended_xmpp_to_tpGuillaume Desmottes2009-08-191-1/+1
|
* parse_result_item: don't leak the info hash tableGuillaume Desmottes2009-08-191-0/+1
|