Thanks!

Make sense to me...



Committed, thanks!

a) You're right, it's not really a bug, I would call it a 
misbehaviour. But feel free to move the ticket to the "Feature Request 
Queue".

b) I'm pleased to hear that atm there is no Horde App using 
searchClients with the $fields param - so this little patch should not 
do any harm at all :-)

c) In my believes API calls to "searchClients" should behave exactly 
like API calls to "search" - with the little difference, that you 
absolutely shouldn't need to know the client address book's name. My 
small modification doesn't do anything else.

d) Motivation: I'm currently modifying Hermes in a way allowing me to 
choose clients from a Search-Popup (similar to IMP's address book 
popup, but simpler). A Dropdown box with thousends of clients is not 
really useful and also putting some heavvy load on our servers ;-)

Not really a bug, as I don't see what is broken here.  This would only 
really matter if we were expecting to perform an OR search on each 
field passed in and I don't see anywhere within the current Horde apps 
where we do that from the client api.



Than being said, I would suggest this as a feature request as we 
should probably do this for future extensibility?



Thoughts?

Currently the $fields parameter of the "clients/searchClients" API 
call requires

us to know the name of the "clients" addressbook (and we don't want to have

to know it). This little patch should fix it.



Cheers,

Thomas Gelf