On Wed, Aug 28, 2013 at 12:18 PM, Duncan Thomas wrote:
> The downside of doing version discovery in the client is that it adds
> a third round trip... though the client can cache the support versions
> I guess.
>
That's only for the Identity version discovery. Add more round trips for
additional
The downside of doing version discovery in the client is that it adds
a third round trip... though the client can cache the support versions
I guess.
On 18 August 2013 00:14, Joshua Harlow wrote:
> +3
>
> Sent from my really tiny device...
>
> On Aug 17, 2013, at 8:33 AM, "Dolph Mathews"
> wrote
+3
Sent from my really tiny device...
On Aug 17, 2013, at 8:33 AM, "Dolph Mathews"
mailto:dolph.math...@gmail.com>> wrote:
On Sat, Aug 17, 2013 at 4:18 AM, Julien Danjou
mailto:jul...@danjou.info>> wrote:
On Fri, Aug 16 2013, Doug Hellmann wrote:
> If you're saying that you want to registe
On Sat, Aug 17, 2013 at 4:18 AM, Julien Danjou wrote:
> On Fri, Aug 16 2013, Doug Hellmann wrote:
>
> > If you're saying that you want to register URLs without version info
> > embedded in them, and let the client work that part out by talking to the
> > service in question (or getting a version
On Fri, Aug 16 2013, Doug Hellmann wrote:
> If you're saying that you want to register URLs without version info
> embedded in them, and let the client work that part out by talking to the
> service in question (or getting a version number from the caller), then
> "yes, please."
Yes yes yes. I al
On 17 August 2013 08:27, Doug Hellmann wrote:
> If you're saying that you want to register URLs without version info
> embedded in them, and let the client work that part out by talking to the
> service in question (or getting a version number from the caller), then
> "yes, please."
That too. Bu
If you're saying that you want to register URLs without version info
embedded in them, and let the client work that part out by talking to the
service in question (or getting a version number from the caller), then
"yes, please."
On Fri, Aug 16, 2013 at 1:47 AM, Robert Collins
wrote:
> We're jus
We're just reworking our endpoint registration on cloud bring up to be
driven by APIs, per the principled separation of concerns I outlined
previously.
One thing I note is that the keystone intialisation is basically full
of magic constants like
"http://$CONTROLLER_PUBLIC_ADDRESS:8004/v1/%(tenant_
