Skip to Content
Last modified by Ravi Mendis on 2012/02/11 08:28
From version 133.1
edited by Ravi Mendis
on 2010/03/04 00:11
Change comment: There is no comment for this version
To version 135.1
edited by Ravi Mendis
on 2010/03/04 00:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,6 +4,12 @@
4 4  
5 5  If you use Scala for a concurrent programming, the chances are that you're using Scala Actor to do that.
6 6  
7 +{{info}}
8 +
9 +Concurrent programming in Scala is based on *Actors* and mailboxes - a common metaphor that is alternatively known as *Message Queues*.
10 +
11 +{{/info}}
12 +
7 7  == Using Scala Actors with EOF ==
8 8  
9 9  EOF being notoriously single-threaded, is incredibly unsuitable for use by Scala Actors.
... ... @@ -12,3 +12,7 @@
12 12  === Using EOAccess to execute SQL ===
13 13  
14 14  Use Wonder API: [[ERXEOAccessUtilities.evaluateSQLWithEntityNamed()>>http://webobjects.mdimension.com/hudson/job/Wonder53/javadoc/er/extensions/eof/ERXEOAccessUtilities.html#evaluateSQLWithEntity(com.webobjects.eocontrol.EOEditingContext,%20com.webobjects.eoaccess.EOEntity,%20java.lang.String)]]
21 +
22 +==== Caveats ====
23 +
24 +If you're updating the state of EOs directly using SQL from Scala Actors, you will subsequently need to refresh/refetch these EOs from the WebObjects application.