[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         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | API extension
  Queue              | Ansel
  Version            | HEAD
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2009-02-16 13:42) wrote:

> I doubt anyone will request image raw data directly or we can encode
> it if you prefer.

IMO, if it's callable via the api, it's callable via jsonrpc and  
xmlrpc so it should be supported and this won't work unless it is  
encoded.

> But we need a way to make it accessible via the API
> to have a full read-write api.

I've been making http requests for the image data whenever I've needed  
to do this - I do this in my iPhoto plugin for example, to get the the  
gallery default images, but I can see the usefulness of having this  
method as well.  I think we should be able to specify the encoding we  
want when requesting the image - the reverse of how the upload works,  
where we need to specify the encoding that we are using during upload.

> OTOH even the browse call sends raw
> data directly.

That might be one of the reasons that I can't get any image data from  
a webdav mount of a remote ansel install...