XSLT & hello

Phillip B Oldham phill at theactivitypeople.co.uk
Tue Apr 8 17:33:50 MSD 2008

I don't think its a definate that the XML tree is going to be loaded 
into memory twice. Some apps might build the XML as a string (ugly, but 
possible), or simply pass-through an existing file. There's even the 
possibility that it might pass-through from a feed of some kind if nginx 
is working as a load-balancer/reverse-proxy.

Given the right features I think such a module would be a great addition 
to a great webserver.

Chris Farmiloe wrote:
> Thanks for all your comments. In summary:
> pros:
>  -- some nice tricks could be done to switch transformation templates
> based on the request (or even not transform at all in the cases where
> clients can do it themselves)
>  -- probably some good opportunities for caching of xsl templates
> cons:
>  -- very likely to be less efficient at nginx level since we would
> have loaded the XML tree into memory twice (once in app server and
> again in nginx to perform transformation)
> Because of my particular need to only process transformations for
> legacy clients, I think a third-party xslt module is still an option.
> But I hadn't thought about the rather pointless double XML parsing, so
> I'll have to think a bit more.
> chrisfarms


*Phillip B Oldham*
The Activity People
phill at theactivitypeople.co.uk <mailto:phill at theactivitypeople.co.uk>



This e-mail and its attachments are intended for the above named 
recipient(s) only and may be confidential. If they have come to you in 
error, please reply to this e-mail and highlight the error. No action 
should be taken regarding content, nor must you copy or show them to anyone.

This e-mail has been created in the knowledge that Internet e-mail is 
not a 100% secure communications medium, and we have taken steps to 
ensure that this e-mail and attachments are free from any virus. We must 
advise that in keeping with good computing practice the recipient should 
ensure they are completely virus free, and that you understand and 
observe the lack of security when e-mailing us.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: phill.vcf
Type: text/x-vcard
Size: 261 bytes
Desc: not available
URL: <http://nginx.org/pipermail/nginx/attachments/20080408/5d2193a4/attachment.vcf>

More information about the nginx mailing list