[horde] Prefs_UI::generateUI($group);

[Chuck Hagenbuch]

Quoting Tom Hodder <tom at scriptsupport.co.uk>:

> The only time I've seen it make a big difference is when outputting table with
> many rows. With a for loop printing table rows, internet explorer flushes
> every time it receives a full row from apache, whereas if the content is
> buffered as block, then internet explorer gets it all in one chunk and it
> displays it in one go. The only difference being that the user gets to see the
> page appearing row by row, rather than waiting for the whole page to load in
> one go.

This can go the other way on you, too. If you buffer the content and then spit
it all out at the end, you end up with *vastly* fewer system calls for I/O, and
Apache can pass the content in as few chunks as possible. So if your table
generation is fast, it will likely appear *faster* when buffered.

> The thing about hackishness is that I noticed that there were some functions
> like purl and url that offered options of print or return, and I was going to
> use a horde function if it was possible. keep it in the family etc. and also
> that I've had some mixed results with different versions of php using output
> buffering.

The url/purl stuff is from way back in php3. I'd actually like to get rid of
those one-line wrappers when echo url() is the exact same thing.

-chuck

--
Charles Hagenbuch, <chuck at horde.org>
"I'm really... I'm not too fascinated by green food." - Average Joe