Re: Post processing
Jacob Smullyan <[email protected]>
| Newsgroups | gmane.comp.web.skunkweb |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Dec 17, 2003 at 11:12:45AM -0500, Adam DePrince, CSA wrote: > There is currently no clean way of catching the output of templating and > applying some sort of post processing filter. I'd added PostProcess > hook to templating.Handler that allows you to modify the outgoing data. > > My motivation was my own itch. I needed created a way of removing \n's > from the html generated by skunkweb. Instead of using spool I figured > that in one effort I would: > > 1. Document and provide a "how to" example on writing a service > 2. To do #1 I wanted to provide something useful, but simple to write, > like an outgoing filtering module. > > I'm hoping that skunkweb-3.5b5.template-postprocess-hook.patch would be > accepted into the skunk sources. I'm definitely agree that post-processing should be easier to do. What you've done seems very straightforward. But it has one drawback -- it only applies the filter to content that emerges from that particular handler. I'd prefer the filter functionality to be more general. I'm in a rush right now, but I'll write more about it later. In the meantime, if anyone wants to sound off on the topic of filters, subrequests, or what have you, this is your opportunity.... j
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/4NhFuqamFyFXXLIRAuOSAJ4xZzwmWIZjtxm4IL6EGP4FjY2c4ACgnUKo JVE+bUzCXSfUecigv+9WL0g= =Pi4y -----END PGP SIGNATURE-----