Second, the server load would multiply if every page that a browser has open on Perlmonks would reload all the time.
You're assuming that a refresh-every-n-seconds is the only way. What I was suggesting was more along the lines of only the chatterbox nodelet updating when the talk button was pressed. The chatterbox is used for more than just chat. Private messages and "you have a reply to ..." style messages are displayed here as well. It would be nice to be able to check the check boxes, hit the talk button, and not have the whole page refresh. In this style, I would venture to guess that the server load would be reduced, both from a CPU standpoint and a bandwidth standpoint. I could be wrong, though.
thor
The only easy day was yesterday
-
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.
|
