Changes for page Building Concurrent Applications with WebObjects and Scala

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,5 +1,7 @@
1		-Given that todays processors ship with dual or quad cores and server processors ship with between 8 to 32 cores, languages like Java, Ruby, Groovy and Python are struggling to keep up. Scala, as its name suggests is built from the ground-up for concurrent programming - a methodology that can take advantage of these modern multi-core processors.
	1	+Given that todays processors ship with dual or quad cores and server processors ship with between 8 to 32 cores, languages like Java, Ruby, Groovy and Python are struggling to keep up.
2	2
	3	+Scala, as its name suggests is built from the ground-up for concurrent programming - a methodology that can take advantage of these modern multi-core processors.
	4	+
3	3	If you use Scala for a concurrent programming, the chances are that you're using Scala Actor to do that.
4	4
5	5	{{info}}
...	...	@@ -20,14 +20,3 @@
20	20	==== Caveats ====
21	21
22	22	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.
23		-
24		-== Alternatives ==
25		-
26		-You may also manipulate the database from outside of the EOF stack.
27		-
28		-=== Squeryl ===
29		-
30		-[[Squeryl>>http://max-l.github.com/Squeryl/index.html]] is a Scala [[Domain-specific language>>http://en.wikipedia.org/wiki/Domain-specific_language]] for SQL.
31		-You may update EOs from Scala Actors using Squeryl instead of using EOF. The advantage here is that you may access the database concurrently avoiding the single-threaded EOF bottleneck in your concurrent application.
32		-
33		-However the same caveat applies - you will need to refresh EOs in the EOF stack for the WebObjects application to reflect the changes made by Squeryl.