Hi Q, I am thinking of using Scala with WebObjects...yes.
Typically deadlocks are more likely to be caused by your own code, rather than the underlying frameworks. This assumes you're using Wonder/WO/EOF in a thread-safe manner. i.e you are taking the necessary precautions for EOF (like turning off shared EOs, auto lock/unlocking of ECs, etc). Broadly speaking, Scala is safer to use than Java for developing a concurrent request handling app because of its lack of static variables and methods, use of separate mutable/immutable datatypes and collections, etc. Using Ajax (i.e asynchronous communication) with WO is where the need for concurrent request handling and better thread-safety come in... Thanks, Ravi On Thursday, September 17, 2009, at 07:10AM, "Q" <[email protected]> wrote: >How does scala improve concurrent request handling in WO? Your session >is going to only allow a single RR to use it at a time. And EOF has >context locks and a giant lock on changes stopping concurrency. If you >go stateless then there is no shared state data between requests >anyway, except whatever you put into Application. Where does the need >for better thread safety fit in? > >Or are you talking about using Lift or something other than WO in your >future projects? _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
