So why not keep the method for the Lift-Actors branch? ... because
there is no concept of linking actors there?
Br's,
Marius
On Sep 24, 6:52 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
I strongly recommend against using scheduleAtFixedRate because:
- Internally, it creates an
Hi,
When you call scheduleAtFixedRate that actor is sending your actor a
Scheduled message, hence you can capture the correct sender. You don't
need to create a different actor.
David's points are quite valid regarding the correct Scala actors'
state.
Br's,
Marius
On Sep 23, 4:17 pm, Xavi
Xavi,
Can you show some code? There might be a way of doing it depending
what you have...
Cheers, Tim
Sent from my iPhone
On 23 Sep 2009, at 20:50, Xavi Ramirez xavi@gmail.com wrote:
Hello,
Is there any way to cancel a task created with a
ActorPing.scheduleAtFixedRate?
From
There isn't much to show... but maybe an example clarify things.
class SomeCometActor extends CometActor {
override def localSetup() {
ActorPing.scheduleAtFixedRate(this, TaskMessage, 15 seconds, 15 seconds)
}
override def lowPriority = {
case TaskMessage =
DoSomething()
I think I figured out a way to get around this:
class SomeCometActor extends CometActor {
private var tempActor: Actor = null
override def localSetup() {
val cometActor = this
var tempActor = actor{ loop { react {
case TaskMessage = cometActor ! TaskMessage
case
