I've been digging around in the object-updater code lately and I noticed that 
unlike the container-updater it does not spawn threads to communicate with each 
primary node. I was wondering if that is on purpose or is it something that I 
can add to it? Seems like it would be a good optimization and fairly easy to 
do. Let me know and I'll do it.

Alex
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to