> --
> Flávio W. Brasil
> http://activate-framework.org
> {persistence as it should be}

> On Saturday, 10 de November de 2012 at 10:33, Konstantinos Kougios wrote:

>> are you sure that this is faster than managing the sync in the database/transaction level? What if you have 3 or 10 servers connecting with the same database?

>> On 09/11/12 12:33, Flávio W. Brasil wrote:
>>> The 1.1 version has a mechanism to coordinate multiple VMs as a distributed STM acessing one database.
>>> Take a look in this spec, it's the same heavy concurrent modification scenario but using multiple VMs, each one with multiple threads:

>>> https://github.com/fwbrasil/activate/blob/master/activate-tests/src/t...

>>> Obs.: The test uses the great gfork framework to create multiple VMs.

>>> --
>>> Flávio W. Brasil
>>> http://activate-framework.org
>>> {persistence as it should be}

>>> On Friday, 9 de November de 2012 at 10:10, Konstantinos Kougios wrote:

>>>> Flavio, thanks for the sample code. I'll have a better look later on but from a quick look I had, here is the question:

>>>> how does activate solve this issue when you have multiple application servers accessing 1 database (or a set of them) ?

>>>> On 09/11/12 11:53, Flávio W. Brasil wrote:
>>>>> Ok, and for me is important to have a safe persistence layer.
>>>>> So, let's consider this as a question of preference. :)

>>>>> --
>>>>> Flávio W. Brasil
>>>>> http://activate-framework.org
>>>>> {persistence as it should be}

>>>>> On Friday, 9 de November de 2012 at 09:29, Tim Pigden wrote:

>>>>>> ah - but for me it's important that "website" is an immutable object and a case class. In that case would I not have to implement a secondary layer on top and we've conceptually just moved the problem from the database | application interface into a activate | rest-of-application interface?

>>>>>> On 9 November 2012 11:12, Flávio W. Brasil <fwbra...@gmail.com> wrote:
>>>>>>> Hello Kostas and Tim,

>>>>>>> Example on why Mapperdao has a veiled mutability:

>>>>>>> https://github.com/fwbrasil/consistency/blob/master/src/test/scala/ma...

>>>>>>> The Activate counterpart:

>>>>>>> https://github.com/fwbrasil/consistency/blob/master/src/test/scala/ac...

>>>>>>> Entity declaration is also much simpler using Activate:

>>>>>>> https://github.com/fwbrasil/consistency/blob/master/src/main/scala/ac...

>>>>>>> Than using Mapperdao:

>>>>>>> https://github.com/fwbrasil/consistency/blob/master/src/main/scala/ma...

>>>>>>> --
>>>>>>> Flávio W. Brasil
>>>>>>> http://activate-framework.org
>>>>>>> {persistence as it should be}

>>>>>>> On Tuesday, 6 de November de 2012 at 20:32, Kostas kougios wrote:

>>>>>>>> Ok, to continue the discussion in this separate thread from https://groups.google.com/forum/?fromgroups=#!topic/scala-user/TNG6KG...

>>>>>>>> ...

>>>>>> --
>>>>>> Tim Pigden
>>>>>> Optrak Distribution Software Limited
>>>>>> +44 (0)1992 517100
>>>>>> http://www.linkedin.com/in/timpigden
>>>>>> http://optrak.com
>>>>>> Optrak Distribution Software Ltd is a limited company registered in England and Wales.
>>>>>> Company Registration No. 2327613 Registered Offices: Orland House, Mead Lane, Hertford, SG13 7AT England
>>>>>> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Optrak Distribution Software Ltd. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error.