<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Concurrent access on data in Web application</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Tue, 21 May 2013 08:40:44 -0400</pubDate>


    <item>

        <title>put the lock in the db</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29510</link>

        

        
            <description><![CDATA[For long transactions, i.e. user views data, user edits data, user hits save I like putting locking info in the db.<br><br>Lock Table: id, record_id, user_id, created, last_modified<br><br>When a user wants to edit data they throw a record in the lock...]]></description>
        

        <pubDate>Thu, 21 Oct 2004 10:08:12 -0400</pubDate>

        

        <jf:creationDate>Thu, 21 Oct 2004 10:08:12 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 21 Oct 2004 10:08:12 -0400</jf:modificationDate>
        <jf:date>Oct 21, 2004</jf:date>
        <jf:author>bruce goldstein</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Concurrent access on data in Web application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29510</link>

        

        
            <description><![CDATA[Frameworks do exist (Toplink for example) which will handle a long gap between read and update. It's not a tricky thing to do although it obviously does have a cost overhead as you (or rather the framework on your behalf) will be checking something in...]]></description>
        

        <pubDate>Wed, 20 Oct 2004 18:46:49 -0400</pubDate>

        

        <jf:creationDate>Wed, 20 Oct 2004 18:46:49 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 20 Oct 2004 18:46:49 -0400</jf:modificationDate>
        <jf:date>Oct 20, 2004</jf:date>
        <jf:author>Duncan Mills</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Concurrent access on data in Web application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29510</link>

        

        
            <description><![CDATA[<blockquote> I'd say just the opposite, let the database handle the locking. </blockquote><br>Unfotunately, this is NOT &quot;Explicit Locking&quot; by application. Row levels locks in a web application are to be handled automatically by the DB and not...]]></description>
        

        <pubDate>Wed, 20 Oct 2004 02:51:08 -0400</pubDate>

        

        <jf:creationDate>Wed, 20 Oct 2004 02:51:08 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 20 Oct 2004 02:51:08 -0400</jf:modificationDate>
        <jf:date>Oct 20, 2004</jf:date>
        <jf:author>Sanjaya Ganesh</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Concurrent access on data in Web application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29510</link>

        

        
            <description><![CDATA[ah, i didn't think about that. <br><br>i come from a background using different dbms's and mysql doesn't offer triggers so i'm always looking for non-db solutions first. the OR layer seems like the most general solution<br><br>luckily i hardly develop...]]></description>
        

        <pubDate>Wed, 20 Oct 2004 01:10:20 -0400</pubDate>

        

        <jf:creationDate>Wed, 20 Oct 2004 01:10:20 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 20 Oct 2004 01:10:20 -0400</jf:modificationDate>
        <jf:date>Oct 20, 2004</jf:date>
        <jf:author>joseph yi</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Concurrent access on data in Web application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29510</link>

        

        
            <description><![CDATA[<blockquote>My suggestion is dont use explicit locks. Explicit row locks in web applications can cause chaos. Imagine, I opening the record and go home for the day leaving the browser open :-).</blockquote>That's a pretty dangerous suggestion, I'd say...]]></description>
        

        <pubDate>Tue, 19 Oct 2004 19:08:21 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Oct 2004 19:08:21 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Oct 2004 19:08:21 -0400</jf:modificationDate>
        <jf:date>Oct 19, 2004</jf:date>
        <jf:author>Duncan Mills</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Concurrent access on data in Web application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29510</link>

        

        
            <description><![CDATA[as i said before, i've never done this... but i still think locking records in the web application using ServletContext is a decent solution and can be used in many ways beyond just locking records (i.e. tracking/monitoring/unlocking records). in the...]]></description>
        

        <pubDate>Tue, 19 Oct 2004 16:03:37 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Oct 2004 16:03:37 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Oct 2004 16:03:37 -0400</jf:modificationDate>
        <jf:date>Oct 19, 2004</jf:date>
        <jf:author>joseph yi</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Concurrent access on data in Web application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29510</link>

        

        
            <description><![CDATA[Vincenzo:<br><br>This is a standard isolation issue with any DB application. Normally, there are two ways in which you can address this:<br><br>(1) Allow the users to manually handle this. Let any number of people update it, it is their responsibility to...]]></description>
        

        <pubDate>Tue, 19 Oct 2004 04:23:43 -0400</pubDate>

        

        <jf:creationDate>Tue, 19 Oct 2004 04:23:43 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 19 Oct 2004 04:23:43 -0400</jf:modificationDate>
        <jf:date>Oct 19, 2004</jf:date>
        <jf:author>Sanjaya Ganesh</jf:author>
        <jf:replyCount>5</jf:replyCount>
    </item>


    <item>

        <title>Concurrent access on data in Web application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29510</link>

        

        
            <description><![CDATA[A simple thing to do would be to 'lock' records by using the ServletContext object to track which record is open for updating. Perhaps you can make an 'AccessLock' object storing the user ID, record ID, and time of lock. When the user is done updating,...]]></description>
        

        <pubDate>Mon, 18 Oct 2004 19:06:44 -0400</pubDate>

        

        <jf:creationDate>Mon, 18 Oct 2004 19:06:44 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 18 Oct 2004 19:06:44 -0400</jf:modificationDate>
        <jf:date>Oct 18, 2004</jf:date>
        <jf:author>joseph yi</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Concurrent access on data in Web application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29510</link>

        

        
            <description><![CDATA[Dear All,<br><br>How Can I revolve concurrent access on data in Web Application<br>More precisely:<br><br>I've two user connected in my application that work on same record.<br>If one of this wait just a minute on change a field in the record and the...]]></description>
        

        <pubDate>Mon, 18 Oct 2004 10:03:09 -0400</pubDate>

        

        <jf:creationDate>Mon, 18 Oct 2004 10:03:09 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 18 Oct 2004 10:03:09 -0400</jf:modificationDate>
        <jf:date>Oct 18, 2004</jf:date>
        <jf:author>Vincenzo Sorrentino</jf:author>
        <jf:replyCount>8</jf:replyCount>
    </item>



</channel>
</rss>

