Get Dynamic Web Content shows a simple demo for Dynamic web contents via HTTPRequest. It could be very easy to implement this at perlmonks for individual modules which frequently update, such as 'chat' or XP nodelet. So instead of loading entire page, we can update individual components of the page. It could be faster for us and can save reasoanble amount of bandwidth and put less load on server.

Replies are listed 'Best First'.
Re: HTTPRequest @ Perlmonks
by hardburn (Abbot) on Feb 15, 2005 at 19:02 UTC

    The problem is that it requires JavaScript. A lot of people have JavaScript turned off for PM (since personal nodes can embed JavaScript and do evil things with PM's cookies).

    So you'd have to make the whole thing optional. Which means you have to do at least a little more work so that users can select which option they're going with. And if few users are going to end up using it, then it sounds like you're going to end up with a lot of work with little gain.

    "There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

[reply]

      Actualy you could have it load the nodelets in the regular way. Then update those with the javascript. No javascript = no auto update. People with javascript on get a little added benifit and everyone else gets exactly what they get now. This is assumeing that we can somehow use a URL to get a single nodelet.

      In my opinion Javascript should be stripped from homenodes anyway, but that is a different story. I'm sure that there are some reasons they are still allowed.


      ___________
      Eric Hodges
[reply]
      Maybe someone can translate the JavaScript into PerlScript?

      It can probably do as nasty things as JavaScript can do, but at least one is being f**d by one's own kind.

      CountZero

      "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

[reply]

        You'd have to implement the XML Request framework, which is a major problem all its own.

        Let's just not download programs from random places and automatically run them, mmmkay?

        "There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

[reply]
        The trouble with PerlScript is that browser support is limited. Very limited. In fact, looking on the ActiveState site it seems that the plugin (which was IE only) isn't available any more.
[reply]
      The problem is that it requires JavaScript. A lot of people have JavaScript turned off for PM (since personal nodes can embed JavaScript and do evil things with PM's cookies).

      Wow. I hope this is frowned upon and any abuse of this "feature" results in some serious ostracism.

      Just curious: Are there some home nodes with friendly and interesting JavaScript that illustrate why JS is tolerated at the Monastery?

[reply]
        Yes. Petruchio.
        Update Sorry for this node. Did not read before posting and answered the Q I thought was asked insted if the one asked.
        And thanks theorbtwo for telling me what to to with stupid nodes like this.
[reply]
Re: HTTPRequest @ Perlmonks
by b10m (Vicar) on Feb 15, 2005 at 21:51 UTC

    I don't think individual nodelet's need frequent updates. Chatterbox is funny, but if you actually want to participate in a conversation, you might aswell use one of the many alternatives.

    XP nodelet I don't need to see updated every 3 seconds (I prefer not to see the loss of XP too often ;).

    --
    b10m

    All code is usually tested, but rarely trusted.
[reply]
Re: HTTPRequest @ Perlmonks
by Aristotle (Chancellor) on Feb 19, 2005 at 02:21 UTC
[reply]

Back to Perl Monks Discussion