On 8 August 2011 22:35, Данило Шеган <email address hidden> wrote:
> I am not familiar with loggerhead code enough (I mostly hack on
> Launchpad), but could you not have your app fetch data from loggerhead
> and then just extract the <body> contents? Then you could run loggerhead
> as strictly the internal service that your app would talk to.
>
Yes, we could send requests into loggerhead, and then parse the
returned HTML, strip out the unwanted parts, and then wrap that inside
our own HTML. However, I consider that approach rather cludgy, and
prone to breakage. I think a better way is to break up the loggerhead
templates into fragments, and allow control overwhich fragments are
rendered - perhaps with a parallel API to the main WSGI interface.
Hi,
On 8 August 2011 22:35, Данило Шеган <email address hidden> wrote:
> I am not familiar with loggerhead code enough (I mostly hack on
> Launchpad), but could you not have your app fetch data from loggerhead
> and then just extract the <body> contents? Then you could run loggerhead
> as strictly the internal service that your app would talk to.
>
Yes, we could send requests into loggerhead, and then parse the
returned HTML, strip out the unwanted parts, and then wrap that inside
our own HTML. However, I consider that approach rather cludgy, and
prone to breakage. I think a better way is to break up the loggerhead
templates into fragments, and allow control overwhich fragments are
rendered - perhaps with a parallel API to the main WSGI interface.
--
Thomi Richards