-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 To echo what Aaron says, in any distributed system, it is almost always a mistake not to design for bulk api calls. Even if you don't think they are needed for the initial use cases, they will almost always be needed at some point later. It is trivial to use a bulk call with a single value, but it is not trivial to go the other way. This topic has been discussed previously in the juju-core space. I had thought that William had (correctly) mandated the bulk calls were to be used for our distributed apis.
On 16/07/14 00:39, Aaron Bentley wrote: > On 14-07-15 10:17 AM, roger peppe wrote: >> The most significant change is that all endpoints refer just to a >> single charm or bundle, rather than being "bulk" calls as they were >> before. > > That sounds like the opposite of what juju-reports wants. Does it > really mean that we would need to make N requests to retrieve info on > N charms? What was the reason for changing this? > > Aaron > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iJwEAQECAAYFAlPGPQsACgkQCJ79BCOJFcb3KgP/fwTB7j+4aR4bFU5F9EU9HUOk HE/IuyEaNrgybDAingF3+ingPJDvYu1/Q2W+DLVVUXjWqosEJbu8NG4qEd/ev5C+ BagEiHD53Ht0jsGZFR6wC6CVVYr3P4u79uO6NsNT6OAEoQi/cXtTws2SC5zpvrCd qsOoQsGhfzSaJmQA8gs= =HThz -----END PGP SIGNATURE----- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
