[dev] Re: dev Digest, Vol 421, Issue 2

[steve]

That would put headers in one place and that would make it easier to 
change. From then, we could have:
- headers for the basic horde framework (a template)
- each application could overwrite this template (just the required elements)

So a page will be made of:
- headers
- common-header.inc
- a specific page
- common-footer.inc

Can I convince you?

Steve

>Zitat von steve <mailling at gmx.co.uk>:
>
> > I wanted to get your opinion about using the PEAR package: HTTP_Header to
> > manage the headers, instead of using directly the function:  header()
> >
> > What do you think about it?
> > If that is fine, I can do the job.
>
>Can you explain what we would gain by using this class? We try to not depend
>on too many external packages as long as they don't bring us enough benefit
>to do so.
>
>Jan.