On Mon, Mar 6, 2017 at 4:11 PM, Perry Gagne wrote:
>
> Doesn't ISC DHCPD use " fixed-address6", "range6", etc for DHCPv6. The code
> you linked seems to be related to "fixed-address" which is the ipv4 variant.
>
This is definitely the case as far as ipv6-specific dhcpd
On Mon, Mar 6, 2017 at 10:11 AM, Martin Bačovský
wrote:
> The current state is that the apipie cache consists of root index page and
> page per API resource and method and JSON desription of whole API
> (multiplied by number of languages). Currently we build all the
On Mar 6, 2017 11:11 AM, "Martin Bačovský"
wrote:
The current state is that the apipie cache consists of root index page and
page per API resource and method and JSON desription of whole API
(multiplied by number of languages). Currently we build all the resource
The current state is that the apipie cache consists of root index page and
page per API resource and method and JSON desription of whole API
(multiplied by number of languages). Currently we build all the resource
specific pages during the package build time. The index and JSON need to
contain
On Mon, Mar 06, 2017 at 10:46:18AM +0200, Ohad Levy wrote:
> On Mon, Mar 6, 2017 at 10:34 AM, Tomas Strachota
> wrote:
>
> > It's used for generating both html doc pages and json (consumed by
> > apipie bindings). We can't get rid of iterating over languages, but
> >
On Mon, Mar 6, 2017 at 10:34 AM, Tomas Strachota
wrote:
> It's used for generating both html doc pages and json (consumed by
> apipie bindings). We can't get rid of iterating over languages, but
> generating docs only in json format and having html page that loads it
> async
It's used for generating both html doc pages and json (consumed by
apipie bindings). We can't get rid of iterating over languages, but
generating docs only in json format and having html page that loads it
async and generates the content dynamically would probably bring the
desired speedup. I like