Locking 'threaded messages'

From: Gerard Seibert (gerard-seibert_at_suscom.net)
Date: 09/29/05

  • Next message: Charles Swiger: "Re: Question about packages"
    Date: Thu, 29 Sep 2005 17:14:23 -0400 (Eastern Standard Time)
    To: freebsd-questions <freebsd-questions@freebsd.org>
    
    

    I was just wondering if I could drum up any enthusiasm for my latest idea
    to improve Becky's overall usability, functional ability and suitability
    to task rating.

    By the way, if this is all ready possible please let me know. I have not
    been able to accomplish it. What I propose is for Carty to incorporate the
    ability to lock a thread either by locking the original message in the
    thread or by implicitly locking any message in the thread and indicating
    that the thread should be locked. By locking, I am referring to making the
    thread immune to deletion unless implicitly unlocked.

    Presently, I have to lock every message in a thread to keep it from being
    deleted when I remove the other garbage in the box the message is located
    in. This is not a problem with Becky's forum since there are usually no
    more than a handful of messages anyway. However, on some forums I belong
    to, I can receive a hundred messages a day. Obviously, I have no use for
    the vast majority of them. Never the less, if there is a thread I want to
    keep, I am forced to lock each message individually. I would like the
    ability to globally lock a thread, in whatever fashion Carty might devise.

    My sole purpose with this post is to see if there is any support for this
    from the other Becky users.

    -- 
    Gerard Seibert
    gerard-seibert@suscom.net
                                                   .:\:/:.
               +-------------------+             .:\:\:/:/:.
               |   PLEASE DO NOT   |            :.:\:\:/:/:.:
               |  FEED THE TROLLS  |           :=.' -   - '.=:
               |                   |           '=(\ 9   9 /)='
               |   Thank you,      |              (  (_)  )
               |       Management  |              /`-vvv-'\
               +-------------------+             /         \
                       |  |        @@@          / /|,,,,,|\ \
                       |  |        @@@         /_//  /^\  \\_\
         @x@@x@        |  |         |/         WW(  (   )  )WW
         \||||/        |  |        \|           __\,,\ /,,/__
          \||/         |  |         |          (______Y______)
    /\/\/\/\/\/\/\/\//\/\\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: Charles Swiger: "Re: Question about packages"

    Relevant Pages

    • Re: using clustered index to optimize inserts ...
      ... I will try to explain locking in terms of Sybase docs... ... Allpages Locking: Allpages locking locks both data pages and index ... the data page is locked with an exclusive lock. ... Clustered Index: The datarows will be arranged as per the clustered ...
      (comp.databases.sybase)
    • Re: CSingleLock - known behaviour?
      ... It is better to design code that doesn't require locking. ... If you don't need the resource, don't lock it. ... magnitude less efficient, than locking once. ...
      (microsoft.public.vc.mfc)
    • Re: Strange multi-user timing phenomenon
      ... table record with pessimistic locking and both edit the same record. ... the recordset will be sufficient to lock out other users. ... update the recordset (if you had to edit data) and then close it. ...
      (microsoft.public.access.formscoding)
    • Re: CMultiLock example
      ... Seriously, though, locking is *mandatory* if two or more threads are accessing non-scalar ... lists ever be modified while the threads are running. ... without a lock. ... You must prevent that one piece of data is modified from multiple ...
      (microsoft.public.vc.mfc)
    • Re: Strange multi-user timing phenomenon
      ... I tried your locking method using a perssimistic recordset and it appears to ... user places his lock and grabs the same record. ... I would try opening a fixed single-row recordset with pessimistic locking, ...
      (microsoft.public.access.formscoding)