Should I send patch here? - xslt_enable "only enable xslt transform for certain user agent"

[tOmasEn]

Not entirely a new feature. just give out more control  to user for current
xslt module. about when or when not to use current xslt module.

It doesn't seems necessarily to me, to fork a new module to publish

On Wed, Jan 27, 2010 at 6:52 PM, Marcus Clyne <ngx.eugaia at gmail.com> wrote:

> Hi,
>
>
> tOmasEn wrote:
>
>> Maybe not many people using xslt as main web layout. but I do.
>>
>> This patch is similar to gzip_disable.  xslt_enable only enable xslt
>> transform for certain user agent.
>>
>> e.g.
>> xslt_enable "Googlebot"
>> will only enable xslt transform output for google's crawler.
>>
>> And, I'm also planing some other improve on xslt module. Like: when xslt
>> transform failed, output original xml file instead of 500 server error; Skip
>> xslt transform if client send specified HTTP header like "No-XSLT", etc.
>> Should I talk to somebody and discuss the architect?
>>
> If you're just adding new features, you're probably better off putting it
> in a separate module and publishing that.
>
> Marcus.
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://nginx.org/mailman/listinfo/nginx
>



-- 
Tomasen
http://twitter.com/ShooterPlayer
http://t.sina.com.cn/Tomasen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20100127/82aaea90/attachment.html>