Skip to Content

Changes for page WebObjects with Scala

Last modified by Ravi Mendis on 2011/05/10 02:10
From version 416.1
edited by Ravi Mendis
on 2010/01/14 22:54
Change comment: There is no comment for this version
To version 419.1
edited by Ravi Mendis
on 2010/01/14 22:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,7 +7,7 @@
7 7  Many of its features and paradigms favor multi-threading and concurrency.
8 8  It could be said that Scala was designed from the ground up for concurrency.
9 9  
10 -Some of these features may not be unfamiliar to Objective-C and WebObjects developers. Here's a summary:
10 +Some of these features may not be unfamiliar to Objective-C or WebObjects developers. Here's a summary:
11 11  
12 12  |= |= Objective-C |= Java |= Scala
13 13  |= Mutable/Immuable Datatypes | Collections //e.g: NSArray/NSMutableArray// | No | Yes
... ... @@ -30,10 +30,10 @@
30 30  With Web 2.0, building concurrent WebObjects applications is a must.
31 31  Developing and maintaining a concurrent or multi-threaded WebObjects application can be challenging.
32 32  
33 -Scala offers concurrency that is (effectively) built-in to the language and is inherently thread-safe.
34 -In other words, developing Ajax (i.e asynchronous communication) with WO will require concurrent request handling and thread-safe code, for which Scala is a better choice than Java.
33 +The lack of static variables means that Scala is inherently thread-safe.
34 +It has concurrency that is effectively built-in to the language in the form of Actors.
35 35  
36 -In addition Scala offers itself as a solution for tasks that typically would have involved threads in a WebObjects application
36 +So for WebObjects developers, Scala offers itself as a powerful, safe and easy-to-use solution for concurrent applications.
37 37  
38 38  === Can WebObjects be Programmed In Scala? ===
39 39