Both of those are exelecent ideas, and I'd look into implementing the first, which shouldn't be all that difficult to do, preferably as an option. (Many people are using iframeless browsers, or have iframes disabled or filtered.) It should help decently much.

The second option would be wonderful, but probably quite difficult to implement -- I don't know of any existing mechinisim to change the HTTP-level response code of everything-generated pages, but it would be quite useful indeed. (However, it may well be implementable, esp since I think (but am not certian...) that everything is rendered, then sent to the browser in one go.)

I'd look into the big question of the second, but I'm rather full of things on my PM-related hacking TODO list -- replyable patches at present. Since, IIRC, you aren't a pmdev, /msg'ing gods is the first step. Then, a week later, start looking at the code -- for the first, at the chatterbox nodelet, for the second Everything/HTML.pm, and the function Everything::HTML::displayPage, and in purticular, exporting something with which nodes can directly effect the arguments to printHeader. (If, at the same time, you create some way to allow for explicit flushes, such that the header and some of the content get output to the client before rendering is actualy complete, you could signifiantly speed up the /precived/ speed of perlmonks (but not the actual speed). The later will be quite difficult, I think, but the former significantly less so -- though my suggested implementation would add another global.


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: 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.