Paolo Ardoino

Are you meaning a map reduce implemention in pigato? I like it! The best thing for me is to create a worker that handles this kind of request. I think...

I think that a worker shouldn't know that a request is map request. I have a couple of questions to better suggest a solution. How do you know that all...

Ok now it's more clear. Thank you. If I've well understood the client receives a single multiplexed steam from the broker that is the result of all the workers streams....

Ok so the client could not have any builtin logic of reducing but receives a stream as normally. I like it.

I have to think why we need a new queue. Starting from the request id the broker could multiplex the streams from multiple brokers in one single steam.

Ok. Let's do this. In the future we may merge the two queues in a more generic one. Can't say before seeing what you have in mind. Thank you

Guys. What about this solution.. - a client send a map request on a particular service (i.e. '$mapreduce'). The request contains in his payload the real service for the request...

For the Client this is totally transparent. We may for example leave the Client send requests to the 'echo' service and specify the option $mapreduce=true in the options object. Basically...

We are not tied to that approach. I'm truly interested in seeing your PR. I've started to work on broadcasting and related thing to reach then the map-reduce functionality, but...

@bmeck could you explain a little bit which are the proposed modifications to the worker and how it can impact the current behaviour. I wish only to remain as generic...