[Date Prev][Date Next][Thread Prev][Thread Next] [Search] [Date Index] [Thread Index]

[MacPerl] BOUNCE macperl-webcgi@macperl.org: Non-member submission from [Michael Geffon <aaa94220@pop11.odn.ne.jp>]



>From macperl@cfcl.com  Sun Feb 20 19:20:20 2000
X-Sent-To: <macperl-webcgi@macperl.org>
Received: from esl.sakuragaoka.ac.jp ([202.235.191.4])
	by cfcl.com (8.9.2/8.9.2) with SMTP id TAA24440
	for <macperl-webcgi@macperl.org>; Sun, 20 Feb 2000 19:20:06 -0800 (PST)
Received: from [165.76.220.74] (HELO pop11.odn.ne.jp) by esl.sakuragaoka.ac.jp (Stalker SMTP Server 1.7) with ESMTP id S.0000014563 for <macperl-webcgi@macperl.org>; Mon, 21 Feb 2000 12:22:01 +0900
Message-ID: <38B0AE8A.2582C5BF@pop11.odn.ne.jp>
Date: Mon, 21 Feb 2000 12:18:35 +0900
From: Michael Geffon <aaa94220@pop11.odn.ne.jp>
Reply-To: aaa94220@pop11.odn.ne.jp
X-Mailer: Mozilla 4.6 (Macintosh; U; PPC)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: macperl-webcgi@macperl.org
Subject: CGI Threading & File Locking
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

Hi,

Can anyone tell me if I need to worry about locking a file used by a
MacPerl CGI script to record submitted form data? No other apps will be
attempting concurrent access.
I've been struggling to determine how people handle locking without an
implementation of flock() on the Mac, but then it hit me that if the
requests are processed sequentially and not concurrently this becomes a non-issue.

Even if I don't have to worry about it in this case, how _do_ I lock a
file under the MacOS should the need arise? There was some discussion on
the list archives about it, but I didn't see a clear answer. Is there an
accepted best practice for exclusive file locking on the Mac?

Thanks!
Michael

# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org