Skip to Content

Changes for page WebObjects with Scala

Last modified by Ravi Mendis on 2011/05/10 02:10
From version 399.1
edited by Ravi Mendis
on 2010/01/17 22:07
Change comment: There is no comment for this version
To version 398.1
edited by Ravi Mendis
on 2010/01/17 19:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,7 +3,7 @@
3 3  Scala is a language for concurrent computing.
4 4  In the day and age of multi-core processors, concurrent computing can't be ignored.
5 5  
6 -Many of Scala's features have been designed with concurrency in mind.
6 +So many of Scala's features have been designed with concurrency in mind.
7 7  Some of these may not be unfamiliar to Objective-C or WebObjects developers.
8 8  
9 9  Here's a quick summary:
... ... @@ -26,12 +26,14 @@
26 26  
27 27  === Why Use Scala? ===
28 28  
29 -Scala is inherently thread-safe.
30 -Because of the lack of static variables developers don't need to worry about synchronising access to mutable shared data.
31 -It has concurrency that is effectively built-in to the language.
29 +Developing and maintaining a concurrent or multi-threaded WebObjects application can be challenging.
32 32  
33 -So for WebObjects developers, Scala offers itself as a powerful, safe and easy-to-use solution for concurrent applications. (In other words, Scala Actors can be used for problems that would have normally required threads).
31 +The lack of static variables means that Scala is inherently thread-safe.
32 +It has concurrency that is effectively built-in to the language in the form of Actors.
34 34  
34 +So for WebObjects developers, Scala offers itself as a powerful, safe and easy-to-use solution for concurrent applications.
35 +(In other words, Scala can be used for problems that would normally have required threads).
36 +
35 35  === Can WebObjects be Programmed In Scala? ===
36 36  
37 37  Yes. It is very simple.