Re: [PHP-DEV] PHP XSLT extension From: Andi Gutmans (andi <email protected>)
Date: 06/25/00

On Sun, 25 Jun 2000, Stefan Livieratos wrote:

>
> -----Ursprüngliche Nachricht-----
> Von: <rubys <email protected>>
> An: Andi Gutmans <andi <email protected>>
> Cc: <php-dev <email protected>>
> Gesendet: Sonntag, 25. Juni 2000 12:00
> Betreff: Re: [PHP-DEV] PHP XSLT extension
>
>
> > Andi Gutmans wrote:
> > >The output buffering is meant for such kind of things. It doesn't require
> > >you to change SAPI modules which means this support will work on all web
> > >servers, instead you can override the output buffering support and add
> the
> > >funtionality.
> >
> > I think the biggest problem to be solved is how to specify which
> stylesheet
> > to be used on a request by request basis. Up until this point, I had been
> > assuming that this needs to be done external to PHP; now I am not so sure.
>
> I am not sure I quite understand this. Do you mean a mechanism for
> automatically
> choosing a stylesheet according to the requesting user agent?

No I mean the PHP script could decide what stylesheet the PHP output
support should use. It just needs to decide before it starts outputting
the data which you want a stylesheet applied to.

Andi

>
> > The cocoon guys found that the pipelining of this data (having the filter
> > consuming it as it is being produced) to be very important - otherwise the
> > web servers memory requirements was excessive and the latency before the
> > beginning of the output was an issue.
> >
> > >I would very much like to see this in PHP.
> >
> > So would I. For the moment, I am going to continue with Cocoon
> > integration, but for the longer term a PHP native implementation of a site
> > map would be worth exploring.
> >
> > I am still interested in hearing if post-processing PHP output was what
> > people had in mind, or if there were other interesting ways in which
> people
> > were thinking of using XSLT.
>
> I am very interested in using XSLT primarily for replacing the various
> template systems which I have tried out:
> - Template part of PHPLIB
> (http://phplib.netuse.de/documentation/documentation-4.php3)
> - Fast Template (http://www.thewebmasters.net/php/FastTemplate.phtml)
> Using XML and XSLT I can send the content raw to XML/XSLT savvy browsers
> like IE 5.0, transform it to HTML for the usual browsers or to WML for
> WAP handys. I could also syndicate my XML content with other sites by
> transforming
> it with XSLT to RSS for example.
>
> Because of XSLT's flexibility and usefulness I hope that Steven Liu's
> Sablotron extension module makes it to the CVS tree soon although it doesn't
> yet
> support the output buffering hooks Andi mentioned. It would be a good
> start and it already works fine!
>
> Regards,
> Stefan
>
>
> 

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
For additional commands, e-mail: php-dev-help <email protected>
To contact the list administrators, e-mail: php-list-admin <email protected>