hi
well I'm mostly going by this stack overflow post.
http://stackoverflow.com/questions/1140448/what-orms-work-well-with-scala
In terms of our requirements, what we want from an orm is fairly basic.
Since we are not building a web application, we would want it decoupled from
any other parts of
We don't accept patches for legal reasons. However, I will upgrade the
module today for you - giving a similar result.
Cheers, Tim
Sent from my iPhone
On 5 Jan 2010, at 04:29, Franz Bettag fr...@bett.ag wrote:
Hey guys,
i've just updated the amqp code. I started a pull request on github
In what way do you mean is mapper worth it?
What kind of system is it? do you need ACID or BASE? What kind of load
will the system be under? Do you need it to be distributed? You are
not restricted to Mapper, you could use JPA or whatever persistence
you want with lift.
If you just want to make
Maybe Akka would be better for you? http://akkasource.org/
Akka has an AMQP module which abstracts AMQP Producer and Consumer as
Actors.
Channing
vishnu-11 wrote:
Hi
I'm trying to use lift to right a back end for a system that
communicates via AMQP. The idea is to have a bunch of
It depends on your use case... you don't really describe exactly what you want
to do. Perhaps start by providing more detail? If you want service teir *only*
though, its quite probable that akka would be a better fix.
Cheers, Tim
On 4 Jan 2010, at 20:30, Channing Walton wrote:
Maybe Akka
well I'm not sure how to describe it differently. As you said it's only
service tier. The truth is I dont know anything about Lift yet and Im just
now running through some basic Scala books.
I need a library with which to talk to rabbitmq as a subscriber that might
work at a higher level than the
Hey guys,
i've just updated the amqp code. I started a pull request on github
but that seems *not* to be the proper way *smirking @dpp's auto-
reply*.
Anyway here is the patch. The problem was that in version 1.5.0 of
rabbitmq's library, the ticket-stuff was removed.
diff --git
