Aye. However, in this purticular case, we could run the opcode (if any), and it could signal somehow "print exactly this content, with no header (because I've included the header), and stop processing after the opcode stage, and before the node stage".

Thanks very much for replying to this, and please, keep doing it -- even if you don't look at the Everything code ever (and it's not really that scary), you're giving me good ideas.

In purticular, currently, opcodes are expected to have a return value that is a bool -- handled, or not handled. We could extend this to say that if they return a scalar ref, then we print that out to the client, and stop processing.

That doesn't give us chunking, but it does mean that some opcodes can avoid having to rerender the page, at least under some curcimstances, with signifiant savings.

Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

In reply to Re: Re: Re: Re: Re: Re: Run your own perlmonks! by theorbtwo
in thread Run your own perlmonks! by theorbtwo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.