Is the Doveadm HTTP API considered stable for production use?

[Felipe Gasper]

> On Aug 23, 2018, at 8:44 AM, Reio Remma <reio at mrstuudio.ee> wrote:
> 
> On 23.08.18 15:35, Felipe Gasper wrote:
>> 
>>> On Aug 23, 2018, at 8:14 AM, James Beck <james.beck at aa.net.uk> wrote:
>>> 
>>>> On Wed, Aug 22, 2018 at 09:54:44AM -0400, Felipe Gasper wrote:
>>>> If you don’t want to use the HTTP API, you can use the raw doveadm protocol.
>>>> 
>>>> https://wiki.dovecot.org/Design/DoveadmProtocol
>>>> 
>>>> -FG
>>> Thanks, I didn't know about that. I suppose testing the HTTP API and
>>> then switching to the raw doveadm protocol over TCP if it turns out
>>> "crashy" wouldn't mean too much work.
>> Why use the HTTP API at all?
> 
> How about JSON. :)

JSON and HTTP headers do make it easy to get started, but they’re inefficient compared to doveadm. JSON in particular limits us to UTF-8 text, so any application that needs to send non-UTF-8 payloads would have to apply an encoding layer. I’ve not looked into the HTTP API, so I don’t know what workaround might be in place to circumvent that limitation.

<shrug> Different strokes for different folks, I guess. :)

-F