XSLT & hello

[Phillip B Oldham]

What would be useful is if you could define the root where the processor 
looks for the stylesheet, and have this seperate from the webroot. For 
instance, if my xsl file was located at:

/var/www/mydocs/xsl/products/default.xsl

And in nginx:

location / {
    root /var/www/mydocs/app/;
    xslt on;
    xslt_root /var/www/mydocs/xsl/;
}

And the output XML:

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/products/default.xsl"?>
<product />

As for whether this should be a bundled or third-party module, I'm with 
mike's comments - while its useful to some people, I wouldn't consider 
it "core" and would be happy to grab it from an external resource.

Chris Farmiloe wrote:
> The main benifit I'm after is being able to decide from the nginx.conf
> something like this (pseudo):
>
> if($user_agent is unable_to_perform_xslt){
>    xslt on;
> }
>
> This would allow me to offload the majority of the XSLT processing
> client-side, but still support some of the older browsers, text-only,
> screen readers etc.
>
> I'm also a fan of a complete separation from application level code...
> although XSL is about presentation, XSLT is simply the process of
> conversion and unlikely to need modifying.
>
> I see you're point about converting between random formats, but if you
> think about it... YES... if there was an XSLT module you could handle
> almost any output you could create with XSL. and maybe even override
> the style-sheet to use ie..
>
> location ~* .csv$ {
>   xslt on;
>   xslt_stylesheet /xsl/csv.xsl;
> }
>
> It could allow you to create application servers that only talk one
> language (XML) while allowing you to still build REST style services
> that respond to multiple content types.
>
> chrisfarms.
>
>
>   

-- 

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

------------------------------------------------------------------------

*Policies*

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/b165f88d/attachment.vcf>