[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

Of course in a perfect world we would like to use the perfect EPFL actors. But as know the world, well at least EPFL actors, are not perfect. By the way: Scala is a lot about libraries, hence IMHO it is OK if Lift uses it's own approach for actors. => Let's go for lift-actor, if possible abstracted

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

I vote for lift-actor. On Wed, Sep 16, 2009 at 10:46 AM, David Pollak < feeder.of.the.be...@gmail.com> wrote: > > > On Wed, Sep 16, 2009 at 7:50 AM, Timothy Perrett > wrote: > >> Kevin, >> >> To clarify, your talking about akka-actors? >> >> The preferred route I think would be to use a fixed EP

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

On Wed, Sep 16, 2009 at 7:50 AM, Timothy Perrett wrote: > Kevin, > > To clarify, your talking about akka-actors? > > The preferred route I think would be to use a fixed EPFL implementation, > however, in leu of that i think from a project perspective it would be > beneficial for lift to have a cor

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

On Wed, Sep 16, 2009 at 4:50 PM, Timothy Perrett wrote: > Kevin, > > To clarify, your talking about akka-actors? > > The preferred route I think would be to use a fixed EPFL implementation, > however, in leu of that i think from a project perspective it would be > beneficial for lift to have a cor

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

Kevin, To clarify, your talking about akka-actors? The preferred route I think would be to use a fixed EPFL implementation, however, in leu of that i think from a project perspective it would be beneficial for lift to have a corrected actor implementation that we have direct control of. I k

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

On Wed, Sep 16, 2009 at 6:27 AM, Kevin Wright wrote: > Is there any reason not to go with something like the Akka framework? I > believe it has a lift-friendly license. I can work on a way to make CometActors work with Akka Actors or Lift Actors. Jonas and I have had a lot of conversations an

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

On Wed, Sep 16, 2009 at 3:42 PM, Naftoli Gugenheim wrote: > > I haven't used comet, but would it be worthwhile to abstract it with > implementations (potentially) for Scala, Lift, and Akka actors? > I've integrated Atmosphere into Akka, and I know that Jeanfranço

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

I haven't used comet, but would it be worthwhile to abstract it with implementations (potentially) for Scala, Lift, and Akka actors? - TylerWeir wrote: Given the on again/off again nature of the issue, I'm voting for adding your change. We can rely on your c

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

What is the problem this time? .. same thing essentially? Br's, Marius On Sep 16, 8:14 am, David Pollak wrote: > Guys, > The Scala Actor issue has raised its head again. > > From November 2008 - June 2009, I did an epic battle with Scala actors and > their memory retention issues. > > I finally

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

Hey David, Are you saying that scala actors are leaking outside of large rate construction / destruction situations? At least, I remember that was what was tickling the EPFL bug last time :-) This has pretty major ramifications if it is! Personally, I'm happy to move to lift-actor. Cheers

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

Given the on again/off again nature of the issue, I'm voting for adding your change. We can rely on your code working until the issue is sorted with the Scala team. So, +1 to dpp's code. On Sep 16, 9:14 am, David Pollak wrote: > Guys, > The Scala Actor issue has raised its head again. > > From

[Lift] Re: Breaking changes in CometActor code vs. continuing instabilities in Scala Actors

Is there any reason not to go with something like the Akka framework? I believe it has a lift-friendly license. On Wed, Sep 16, 2009 at 2:14 PM, David Pollak wrote: > Guys, > The Scala Actor issue has raised its head again. > > From November 2008 - June 2009, I did an epic battle with Scala act