[Tickets #12740] Re: Better return from search API call

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12740
------------------------------------------------------------------------------
  Ticket             | 12740
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Better return from search API call
  Queue              | Turba
  Version            | Git master
  Type               | Enhancement
-State              | Rejected
+State              | Feedback
  Priority           | 1. Low
  Milestone          | 5
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-10-07 12:09) wrote:

> Anything returned from the API should be compatible with a RPC call  
> as well. Requiring logic in the returned object to access the  
> requested data will not work over e.g., json-rpc calls.

Huh?  How is this supposed to work?  See mail/imapOb - that returns a  
Horde_Imap_Client_Base object.  That is most certainly NOT something  
that can be returned via a JSON-RPC call.  (or mail/flagList.  Or  
mail/createMailbox).

And that is extremely concerning if you are saying that  
inter-application API calls are restricted to simple data structures .  
  That is a **crippling** limitation for a feature that came AFTER the  
original API design - which allowed PHP objects to be returned.

If you disgaree, than there needs to be a separate RPC framework in  
the future.  Or at least a separate search call that is RPC specific.

But you absolutely cannot be expected to know the structure of the  
photo data object, so at a minimum this ticket cannot be closed.  This  
needs to be documented somewhere.