in reply to Re: Quick Note ordering Switches.
in thread Quick Note ordering Switches.

another server hit, and I'd prefer to minimize them.
I'd say adding this feature will minimize server hits. Switching the method how to order replies is already possible, except that it requires several server hits (go to user settings, change user settings, go to original page, then go back to the user settings, undoing the setting).

Not that I care whether such a feature is implemented - I always prefer threaded/oldest first sorting.

Abigail

Replies are listed 'Best First'.
Re: Re: Quick Note ordering Switches.
by theorbtwo (Prior) on Oct 20, 2003 at 10:27 UTC

    Ah, yes, but the current way is difficult enough that it serves as a deterrent from doing it at all. I suspect, then, adding the feature would create more load then it removes, and at the current state of the monestary, I'll take speed over useability.

    Oh, BTW, have you seen Monastery NNTP Bridge? It's woefuly incomplete, but looks quite interesting, esp as you've often mentioned that you'd like such a thing. (I /msg'd you too, but you apparently don't read them.)


    Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

      I'd think this would be used mostly by power users not by the average monk. Thus, it would not add too many database hits. OTOH, you could argue that for that reason it shouldn't be added as a feature....

      Also, I have no idea how the PM engine works, but are nodes cached as they are displayed? If they are, then the hits would be minimal, because by definition the page has already been displayed. (If they aren't cached, why not?)
      ----
      May your tongue cleave to the roof of your mouth with the force of a thousand caramels.

        Nodes are cached, however, we check the cached for freshness every hit, which decreases the effectiveness of the cache saddeningly. I've got several schemes brewing on this, and tye has some as well, but none are anywhere close to ready.


        Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).