Home/ Questions/Q 670611
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T00:16:59+00:00

Is this a good method to save to all index in a variable and

  • 0

Is this a good method to save to all index in a variable and then echo this? for example

<?php
    $txt='<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-9" />
   <link rel="stylesheet" type="text/css" href="css/style.css"/>
   <title>Untitled Document</title>
   </head>

   <body>
  <div class="wrapper">
      <div class="header">
        <h2>'.heaf_func().'</h2>
      </div>
      <div class="content">content</div>
      <div class="footer">footer</div>
  </div>
  </body>
  </html>';
  echo $txt;

?>
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Generally, no. If you need to do output buffering, just use the output buffering API. Even if you need to retrieve your output to do post-processing on it, you can do that using ob_get_contents. It won’t be a big deal on most pages, but on large pages or under heavy server load you should use the output buffering support because it’s better optimized for what you’re trying to accomplish.

    Generally, when looking at a method such as what you’re contemplating, ask yourself “what does this gain me?” Your example above is clearly trivial, but unless you’re planning on post-processing your results, what does it gain you?

    EDIT:

    I’ve used both the PHP-in-XML and XML-in-PHP approaches in various projects. My experience is that on a project of any significant size the PHP-in-XML (or HTML, but I try to always generate XML or XHTML) eventually turns into nasty spaghetti code that becomes a pain to maintain, whereas the XML-in-PHP approach eventually balloons into a mess of string-manipulation code that you also don’t want to maintain.

    Generally, I’d recommend going with an MVC (MVVM, MVP, etc. – up to you) framework for every web app, regardless of language. If applied correctly, the additionally framework complexity is more than compensated by the modularity and ease of maintenance and extensibility that you gain. If you don’t feel the need or desire to target a framework (though, again, I STRONGLY recommend it), I typically follow these rules:

    1. Whenever possible, limit PHP-in-XML to simple inclusion of values. E.g., <h1><?php echo $title; ?></h1> Try to avoid including logic in your spaghetti code (other than, perhaps, repetition, though I typically abstract that away, too).
    2. Whenever possible, create XML documents using the XML API’s instead of writing raw values to the output. XML has the advantage of being easily transformable, which in my experience is well worth the extra initial investment, at least in production apps.
    3. Send the client an XML document representing your data with an xml-stylesheet processing instruction indicating the location of a stylesheet to apply for rendering and let the client do its own rendering. Failing that, put your data-to-presentation transformation logic in a stylesheet (XSLT, not CSS) and do the transformation server-side. I really enjoy the separation between data and presentation it allows me.
    • 0