[sheepdog] [RFC] REST gateway design choice

[Joseph Glanville]

I like MHD if I have to choose a prebuilt and well supported HTTP
implementation. http://www.gnu.org/software/libmicrohttpd/
It's supports threaded and evented modes of operation along with a
combination of the 2 which is very fast.

If libev/libuv eventloops are tolerable the NGINX http parser combined
with a simple tcp server implementation is also a great option but is
more custom.

Joseph.

On Mon, Jul 1, 2013 at 11:58 PM, MORITA Kazutaka
<morita.kazutaka at gmail.com> wrote:
> At Mon, 1 Jul 2013 13:04:20 +0800,
> Liu Yuan wrote:
>>
>> >
>> > >      - simpler interface, just start 'sheep' as usual we gain REST gateway
>> > >        function, no extra parameter needed.
>> >
>> > I think we need a parameter to enable (or disable) the REST gateway
>> > for the users who don't use the interface.
>> >
>>
>> I think of always-enable because if people won't use it, it only takes one extra
>> thread sleeping.
>
> Another concern to enable the feature always is that the REST api
> support will introduce additional requirements to build sheepdog
> binary.  What libraries are required for the REST gateway
> implementation?
>
> Thanks,
>
> Kazutaka
> --
> sheepdog mailing list
> sheepdog at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/sheepdog