HP3000-L Archives

November 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
RON HORNER <[log in to unmask]>
Reply To:
RON HORNER <[log in to unmask]>
Date:
Wed, 18 Nov 1998 17:20:49 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
The single problem that I find with unconditional locking is the human
element.  Someone walking away as the lock is applied.  Basically hard
locking data so that no one else can get to it.

The other point is keeping track of what programs are doing what kinds
of locking.  If a program that conditionally locks a record and another
program that does hard locking tries to lock the same record, make sure
there is something in the hard lock program to keep trying and not blow
up.

That's it for me.

        -----Original Message-----
        From:   Greg McDaniel [SMTP:[log in to unmask]]
        Sent:   Wednesday, November 18, 1998 4:57 PM
        To:     [log in to unmask]
        Subject:        TurboImage Locking

        Could someone tell me if there are any problems with some
programs doing
        conditional item level locks while other programs are doing
        unconditional item level locks.  The programs are all locking
the same
        item.  All of our code currently use conditional item locks but
we would
        like to move to unconditional locks for some applications.
Hence we
        would end up with a mixture of conditional/unconditional item
locks.

        TIA

        Greg

ATOM RSS1 RSS2