So what would be the scenario where you have two actors, one, the
reader, reading stdin, and sending to the other, the writer, which
then processes it line by line and writes stats? They're now started
in the main driver with start(), the reader, upon EOF, sends a special
EXIT message to the
On Tue, Nov 17, 2009 at 11:04 AM, braver delivera...@gmail.com wrote:
So what would be the scenario where you have two actors, one, the
reader, reading stdin, and sending to the other, the writer, which
then processes it line by line and writes stats? They're now started
in the main driver
On Nov 17, 2:26 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Neither Lift Actors nor Scala Actors are meant for blocking IO. So, reading
in an Actor is just going to be pain. You're a lot better off using a
thread for reading and a separate thread for writing.
My reading actor is
On Nov 17, 2:26 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
There's no such thing as shut down for Lift Actors. They are like any
other object in your JVM. They respond to messages and when there are no
more references to them, they get garbage collected.
I'm probably belaboring
On Tue, Nov 17, 2009 at 12:34 PM, braver delivera...@gmail.com wrote:
On Nov 17, 2:26 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
There's no such thing as shut down for Lift Actors. They are like any
other object in your JVM. They respond to messages and when there are no
You mean you didn't implement your own GC on top of the JVM's GC? Where's
your sense of adventure...
On Mon, Nov 16, 2009 at 1:35 AM, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Sun, Nov 15, 2009 at 10:29 PM, braver delivera...@gmail.com wrote:
I have a simple question on
I have a simple question on migrating a typical PinS-desribed pattern:
def act() =
loop {
react {
case DoSomething = ...
case EXIT = exit()
}
}
-- now, without exit(), how does it terminate?
Cheers,
Alexy
--~--~-~--~~~---~--~~
You received this
On Sun, Nov 15, 2009 at 10:29 PM, braver delivera...@gmail.com wrote:
I have a simple question on migrating a typical PinS-desribed pattern:
def act() =
loop {
react {
case DoSomething = ...
case EXIT = exit()
}
}
-- now, without exit(), how does it terminate?
Like any other
David,
I attempted to follow your blog piece and rewrite the code in
Integrating Flex, BlazeDS, and Scala/Lift, at http://flexonrails.net/?p=103.
Maybe I'm being a bit ambitious to redo this, but when I run just the
Lift portion (without Flex/BazeDS) and make a call to my LiftActor
One small step for Lift and Akka, one giant leap for Scala!
Thanks, David and Jonas!
Heiko
2009/10/22 Marius marius.dan...@gmail.com
Just Simple Beautiful ! ... Nice work Dave and Jonas.
Br's,
Marius
On Oct 22, 9:57 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Folks,
I
Stickied for now, until we think it's no longer an issue.
On Oct 22, 2:57 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Folks,
I wrote a quick blog piece about migrating from Scala Actors to Lift Actors
athttp://blog.lostlake.org/index.php?/archives/96-Migrating-from-Scala-...
I
Thanks to David for the migration guide. It is very useful.
Victor Klang had raised the issue of rescheduling the actor in the
message handling function (see below). I did not see a reference to
this in the migration guide. Is it still necessary?
Thanks in advance.
Dan
Text from Victor
Just Simple Beautiful ! ... Nice work Dave and Jonas.
Br's,
Marius
On Oct 22, 9:57 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Folks,
I wrote a quick blog piece about migrating from Scala Actors to Lift Actors
13 matches
Mail list logo
