Ability to render HTML page fragment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
loggerhead |
Triaged
|
Low
|
Unassigned | ||
loggerhead-breezy |
Triaged
|
Low
|
Unassigned | ||
sloecode |
New
|
Undecided
|
Unassigned |
Bug Description
It would be nice to have some sort of API in loggerhead to control exactly which parts of the HTML page is rendered.
Currently it's not easy to integrate loggerhead with a second WSGI app - requests must be either fully served by loggerhead or by the original app, which removes the possibility of showing loggerhead-
If there was some form of API inside loggerhead so I could effectively say "Here's a branch, render this view (changelog, for e.g.) to HTML, with this path prefix, and give me the results" it would be trivial to integrate loggerhead with other web-apps in a sane manner.
Unfortunately, after having poked around in the loggerhead source, i can't see a trivial way to get this done.
Changed in loggerhead: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in loggerhead-breezy: | |
status: | New → Triaged |
importance: | Undecided → Low |
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.