On 07.04.02 (12:33), [EMAIL PROTECTED] wrote:
> > Would it fulfill your requirements doing it the other way
> > round, by calling your outside applications via
> >
> > include("/path/to/application.php");
> >
> facing simillar problem I found that you cannot use this
> syntax if your "application.php" uses header generating
> procedures (cookies, session etc.) because your style will
> produce headers first..
Right.
> or ypu have to make code-inits to every such page. I just made
> special midgard pages like, say, "topbar" including some
> midgard action and incldue them within "application.php" by
>
> include ("http://olga.pl/specials/topbar.php";);
>
> what gives me my layout from midgard style, but right after
> "application.php" sent headers. Disadvantage is that such
> include produce unnecessary log entries.
And performance overhead.
If the header-generating parts of your "application.php" are
easily separated from the rest, you may also include it two-
staged:
<[code-init]>
include("/path/to/application-init.php");
<[content]>
include("/path/to/application-show.php");
Hope that helps,
phr
--
Linksystem Muenchen GmbH [EMAIL PROTECTED]
Schloerstrasse 10 http://www.link-m.de
80634 Muenchen Tel. 089 / 890 518-0
We make the Net work. Fax 089 / 890 518-77
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
