It is most suitable for parallel processing where you have lot of tasks that
can be independently processed.
If your tasks have shared states things are going to be more complicated.
Fortunately this is changed
with languages like Scala/Clojure. In both you have STM(Software transaction
memory ) ap
So, fundamentally, it's an architecture for dealing with "trivially
parallel" problems? Would that be an accurate summary?
(Not to imply your problems are trivial.)
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email t
My company have made system based on some kind of such architecture.
It is parkng service for cites. You have parts of some streets where parking
is allowed. That parts have name and phone number. For example
Zone 1 and 9111. People use mobile phones for pay parking.
They send sms message to 9111 n
I've used something along these lines in the past for a medical
imaging app. We needed to pre-fetch images and possibly pre-process
them (filter, apply overlays) so that as a user was scrolling through
an image set it was smooth and they weren't waiting for images to be
processed. The GUI handler
At the risk of sounding incredibly uneducated about the matter (oh wait,
it's true):
What is the purpose/need/reason for this kind of architecture? What can you
do with it? Where would you use it? Why would you use it?
Thanks,
Jonathan
--
You received this message because you are subscrib
On Feb 28, 3:34 pm, Zlaja wrote:
> How I can achieve master worker pattern in clojure with agents.
> For example I have components that write messages to a queue.
> I would like to process messages parallel by agents. Is it posible?
This use case sounds like a job for Lamina:
https://g
You might find the (totally unsearchable) "work" library to be useful:
https://github.com/getwoven/work
On Feb 28, 11:38 am, Zlatko Josic wrote:
> Hm. I need something like pool of agents something ilke
> akka framework for scala/java. So I can process more
> messages at once.
>
> Zlaja
>
>
>
>
Hm. I need something like pool of agents something ilke
akka framework for scala/java. So I can process more
messages at once.
Zlaja
On Mon, Feb 28, 2011 at 6:34 PM, Ken Wesson wrote:
> On Mon, Feb 28, 2011 at 12:31 PM, Zlatko Josic
> wrote:
> >
> > First thanks for reply.
> > if I use only o
On Mon, Feb 28, 2011 at 12:31 PM, Zlatko Josic wrote:
>
> First thanks for reply.
> if I use only one agent does it mean that the
> agent process one message by one?
Yes. And messages sent from the same thread will be processed in the
order that that thread sent them, also.
--
You received this
First thanks for reply.
if I use only one agent does it mean that the
agent process one message by one?
Thanks
Zlaja
On Mon, Feb 28, 2011 at 4:26 PM, Ken Wesson wrote:
> On Mon, Feb 28, 2011 at 9:34 AM, Zlaja wrote:
> > Hi,
> >
> > How I can achieve master worker pa
On Mon, Feb 28, 2011 at 9:34 AM, Zlaja wrote:
> Hi,
>
> How I can achieve master worker pattern in clojure with agents.
> For example I have components that write messages to a queue.
> I would like to process messages parallel by agents. Is it posible?
>
> Thanks
It may b
Hi,
How I can achieve master worker pattern in clojure with agents.
For example I have components that write messages to a queue.
I would like to process messages parallel by agents. Is it posible?
Thanks
Zlaja
--
You received this message because you are subscribed to the Google
Groups
12 matches
Mail list logo
