One of the huge drawbacks in beginning serious use of Scala is the
lack of an accepted and documented way to talk to the databases such
as PostgreSQL. Googling for scala.dbc examples pulls old stuff from
2007; there's a scala-query on github, which is promising, and
abandoned dbc2, and dbc3
On May 22, 7:06 pm, Timothy Perrett timo...@getintheloop.eu wrote:
Hey there,
Is their a particular reason you wouldn't or couldn't use existing java
persistence infrastructure inside your scala application? That's the
recommended advice right now; JPA (for instance) will slot right into
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
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 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
Perhaps I'm not looking in the right place, but I didn't find the
scaladocs alongside the jars and source.jars for Lift in the usual
maven repo.
Are we supposed to use scaladoc manually, or IDEs, to generate the API
docs?
Also, I'm interested in liftweb-actor separately, and see its jar and
