Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Date: Mon, 14 Apr 2003 09:30:34 -0400
From: Jim Krygowski <james.krygowski@shaws.com>
Subject: RE: Maybe OT: File Locking and Tomcat
In-reply-to: <9C5166762F311146951505C6790A9CF858E89B@US-VS1.corp.mpi.com>
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Message-id: <KCEJJEECFLHDJDJEMOFOEENCEFAA.james.krygowski@shaws.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal

Have you thought about using the java.nio.channel package?  I haven't dug
into it yet but I've read a few articles.  You might be interested in
looking at SelectableChannel.

> -----Original Message-----
> From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
> Sent: Monday, April 14, 2003 9:14 AM
> To: Tomcat Users List
> Subject: RE: Maybe OT: File Locking and Tomcat
>
>
>
> Howdy,
>
> >I'm implementing a web app using Tomcat 4.1 running on linus with JDK
> >1.3 and currently my client doesn't want to use a database to store
>
> This is not always a bad thing! ;)
>
> >A potential solution I'm looking into involves checking for a lock file
> >(like my-file.csv.lock).  If it doesn't exist, I create it, then write
> >to the CSV, otherwise, I wait til the lock file doesn't exist.
>
> This is a good solution as it's platform-independent,
> database-independent, lightweight, and self-contained within your
> webapp.  I would make two small suggestions:
>
> - Use the javax.servlet.context.tempdir directory for the lock file, as
> this is the one (actually you could use java.io.tmpdir as well) place
> you're guaranteed write permissions.
>
> - Either don't wait for the lock file to not exist, instead putting a
> message to the user to try again later, or wait for a very short time.
> Don't get into a state that could appear as 'hung' to the user.
>
> Yoav Shapira
> Millennium ChemInformatics
>
>
>
> This e-mail, including any attachments, is a confidential
> business communication, and may contain information that is
> confidential, proprietary and/or privileged.  This e-mail is
> intended only for the individual(s) to whom it is addressed, and
> may not be saved, copied, printed, disclosed or used by anyone
> else.  If you are not the(an) intended recipient, please
> immediately delete this e-mail from your computer system and
> notify the sender.  Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org