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.agra...@rackspace.com<mailto:roshan.agra...@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.all...@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@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
