Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (11)
As of 2023-05-30 14:17 GMT
Find Nodes?
    Voting Booth?

    No recent polls found