Instead of:
class MyActor extends Actor {
makeTransactionRequired …
}
woudn't it be clean to have:
trait TxRequired
{
self : TransactionManagement =>
makeTransactionRequired
}
class MyActor extends Actor with TxRequired
{
}
On Mon, Jul 13, 2009 at 11:04 AM, Jonas Bonér <[email protected]> wrote:
>
> Hi.
>
> On Jul 13, 9:51 am, Timothy Perrett <[email protected]> wrote:
> > From what I can see, its not just about concurrency, right? STM is
> probally
> > used in conjunction with Cassandra...?
> >
>
> Right. Even though messages in the actor model are immutable the
> actors are not. If they were they would be almost useless.
>
> The actor model is great for some use cases but terrible for others. I
> have many times felt like I would like to have a transactional
> compositional message flows. This is an attempt to solve that problem
> (and some other problems as well).
>
> The STM is working with managed data structures like TransactionalMap/
> Vector/Ref. Accessing them outside a tx yields an error. The STM also
> understand and works with asynchronous messaging something that is not
> trivial.
>
> I think there is some synergy between both Lift and Goat Rodeo. Would
> love to see what could come out of that. I am open for all suggestions/
> crazy ideas.
>
> Thank, Jonas.
> > Cheers, Tim
> >
> > On 13/07/2009 07:25, "marius d." <[email protected]> wrote:
> >
> > > I wonder why STM in a message passing concurrency model where things
> > > supposed to be immutable.
> >
>
--
Viktor Klang
Java Specialist
Scala Loudmouth
Lift Committer
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---
