Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I used to work for a company that did essentially what you are suggesting above for their major product. Content was written in XML, and was transformed into HTML using XSLT depending upon user settings. This meant that it was possible to do radically different things for different users, whereas the writers of content had a very easy time with a generalised mark-up language. Sounds a bit like how HTML was supposed to be, doesn' t it?

All the XML to HTML transformation was done server-side, which does incur a very serious performance hit. In the case of this particular product, pages consisted of many well-defined objects, and once these were rendered once for a particular user profile, those objects could be agressively cached. This meant that things could still run at reasonable speeds, despite the performance hit of the XML to HTML pipeline.

PerlMonks is blessed with a similar structure of well-defined objects. We have nodes and nodelets, most of which remain fairly static (with a few exceptions). Being able to agressively cache and assemble these objects, rather than doing a full transformation with XSLT, would no doubt make an XML backend much more possible without major hardware upgrades.

If the PerlMonks code does not already do so, I would strongly suggest thinking about caching strategies for both XML and rendered HTML code. This might even provide performance benefits even if we did stay with a pure HTML website.

What Petruchio is discussing is possible and is certainly worthwhile. Just make sure you don't burn a hole through your CPU in the process. :)


In reply to Re: Learn to be a pmdev vigilante in 21 days! by pjf
in thread Learn to be a pmdev vigilante in 21 days! by Petruchio

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    [Corion]: Meh. My lack of embedded Pg is showing. I can get the data for an image gallery with one SQL statement, but not with SQLite as it doesn't do window functions :-(
    [Corion]: Hmmm. Maybe I can still fake the one spot where I want/need a window function in SQLite... I think I'm never really interested in the real "next" image (not hidden/deleted)

    How do I use this? | Other CB clients
    Other Users?
    Others exploiting the Monastery: (6)
    As of 2018-03-23 17:53 GMT
    Find Nodes?
      Voting Booth?
      When I think of a mole I think of:

      Results (295 votes). Check out past polls.