Open Stack

No, I was Infact thinking about making all responses synchronous to keep things simple in the beginning. Mostly because I can't think of any use case that requires asynchronous processing right now. But you're right, we might want to support async right from the start.




On Nov 27, 2013, at 1:36 PM, "Roshan Agrawal" <roshan.agrawal at RACKSPACE.COM<mailto:roshan.agrawal at RACKSPACE.COM>> wrote:

We should probably include support for asynchronous responses right from the beginning to handle calls that need a long time to process. Is this in line with what you were thinking ? I am referring to your comment in the blueprint “To start things off, we can implement workflow #1 shown above and make all requests synchronous”

From: Murali Allada [mailto:murali.allada at RACKSPACE.COM]
Sent: Wednesday, November 27, 2013 12:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Solum] API worker architecture

Hi all,

I'm working on a new blueprint to define the API service architecture.

https://blueprints.launchpad.net/solum/+spec/api-worker-architecture

It is still a draft for now. I've proposed a simple architecture for us to get started with implementing a few useful use cases.

Please chime in on the mailing list with your thoughts.

Thanks,
Murali
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131127/bd5af7b4/attachment.html>