:34 am, vishnu path...@gmail.com wrote:
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
, then sure, Lift
will be fine. Akka works well when you need fault tolerance or
distributed nodes etc etc
Cheers, Tim
On Jan 5, 3:34 am, vishnu path...@gmail.com wrote:
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
,
bytes.toByteArray)
+channel.basicPublish(mult, routeroute, null,
bytes.toByteArray)
}
}
On 5 Jan., 04:34, vishnu path...@gmail.com wrote:
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
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 (threads?,
processes? actors?) that subscribe to some queues on a queueing system
and react to various messages by contacting various third party
systems and persisting messages
:
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
