zmq-omdp
zmq-omdp copied to clipboard
prdn
Name change and future of the project
Hi everybody
I'd like to bring this project towards implementing new features
- authentication : broker side and worker side
- broker requests queueing: I want to move the actual in memory array based queue to a class extendible so that we could have a redis based queue manager for persistent requests.
- broker reply caching : I'd like to have a flag defined by a worker that defines if a given reply generated by itself could be cached by the broker so same client requests could be replied automatically by the broker. There should be also a timeout for those cached replies.
Name change... I'm thinking that we should change the name is something more funny and more easier to remember. I propose Pigato a quality of grapes in Italy. The concept of grapes is similar to distributed workers so I like it. Also the logo can be a couple of grapes.
The repository name will change according to the new name.
What do you thing about this?
Great ideas Paulo, I think these new performance enhancing and time saving features sound amazing! Name sounds cool to!
On Thursday, 9 October 2014, Paolo Ardoino [email protected] wrote:
Hi everybody
I'd like to bring this project towards implementing new features
authentication : broker side and worker side
broker requests queueing: I want to move the actual in memory array based queue to a class extendible so that we could have a redis based queue
manager for persistent requests.
broker reply caching : I'd like to have a flag defined by a worker that defines if a given reply generated by itself could be cached by the broker so same client requests could be replied automatically by the broker. There should be also a timeout for those cached replies.
Name change... I'm thinking that we should change the name is something more funny and more easier to remember. I propose Pigato a quality of grapes in Italy. The concept of grapes is similar to distributed workers so I like it. Also the logo can be a couple of grapes.
The repository name will change according to the new name.
What do you thing about this?
— Reply to this email directly or view it on GitHub https://github.com/prdn/zmq-omdp/issues/7.
- Sent with best regards from my iPhone
@prdn seems fine; I would still follow the titanic protocol for queueing for now (I work w/ big corps who want everything well known if possible). We will be using this for a long time and I would like to add encryption to the list if possible (I will get to it eventually).
What auth strategy did you think you wanted to use? Or something flexible?
@bmeck Yes. Titanic could be the solution for persistent requests. For encryption and authentication I think we should try to integrate libcurve https://github.com/zeromq/libcurve and zap But I would also add hooks for Broker and Worker so that they could decide if accept a request connecting for example to a database server or whatever.
pigato is here :) https://github.com/prdn/pigato I have refactored examples and a bit of documentation the help new developers to use the platform. I'm going to publish also some real-world examples.
please use static linking for any libraries used
On Fri, Oct 10, 2014 at 9:50 AM, Paolo Ardoino [email protected] wrote:
pigato is here :) https://github.com/prdn/pigato I have refactored examples and a bit of documentation the help new developers to use the platform. I'm going to publish also some real-world examples.
— Reply to this email directly or view it on GitHub https://github.com/prdn/zmq-omdp/issues/7#issuecomment-58666256.