[Tickets #7974] Re: API extension

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/7974
------------------------------------------------------------------------------
  Ticket             | 7974
  Updated By         | Duck <duck at obala.net>
  Summary            | API extension
  Queue              | Ansel
  Version            | HEAD
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Michael Rubinsky
+New Attachment     | api.diff
------------------------------------------------------------------------------


Duck <duck at obala.net> (2009-02-16 10:55) wrote:

> 1) The return datatype in the signature for getImageContent is incorrect
>
> 2) All parameters with default values in a function signature must
> follow all parameters that do not have a default value.
>
> 3) Your not checking age restrictions or password protected galleries
> before returning the image data.

Fixed...

> That being said, I'm not so sure this api method is a good idea -
> will sening the raw, binary image data actually work over XML/RPC or
> JSON/RPC?

I doubt anyone will request image raw data directly or we can encode  
it if you prefer. But we need a way to make it accessible via the API  
to have a full read-write api. OTOH even the browse call sends raw  
data directly.