Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
You make some good points about the transitory nature of the chatterbox, I can't argue with the examples you cite.

Perhaps what I really want is not a permanent logging of the comments for posterity, but a larger window into the discussion. I guarantee that I am not the only person who has logged on and caught the end of what looked like an interesting discussion. A lot of times, I would like to see what has been said already without everybody repeating themselves. Or perhaps someone has asked a question and all you have seen are the replys, again a larger window into the discussion would be useful.

A one hour cache would suit my purposes much better than a permenant record. A one hour cache would also allay most of the concerns about losing context. So if we had a page that showed the previous hour's discussion, would this be a better solution acceptable to all/most?

update Ok I realise very few people have actually read this post since I wrote it, but this seemed worth adding.

There is a separate discussion going on about chat scripts logging in while they poll for messages. ZZamboni has mentioned that (in order to ensure he does not miss anything) he leaves his script running while he is not there. If there was a "previous hours chat" page, you could amend the polling frequency of your chat scripts to once every 55 - 58 minutes or so, when you were leaving them unattended. This would greatly reduce the load on the server.

Thanks for reading


Baldrick, you wouldn't see a subtle plan if it painted itself purple and danced naked on top of a harpsichord, singing "Subtle plans are here again!"

In reply to RE: Is it a good idea to log the chatterbox by nuance
in thread 24Hr log of chatterbox by jjhorner

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
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others rifling through the Monastery: (7)
    As of 2021-01-26 06:36 GMT
    Find Nodes?
      Voting Booth?