OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [xdi] names of the bindings?

I think 1. should reflect that it is a single message envelope which gets a single reply - I’m pretty sure we will want a persistent session binding as soon as we have to face performance issues.

On the redirect bindings, I’ll defer to everyone else’s opinions until I understand them better.

On Sep 22, 2014, at 9:31 AM, Davis, Peter <Peter.Davis@neustar.biz> wrote:


On Sep 21, 2014, at 15:22 PM, =Drummond Reed <drummond.reed@xdi.org> wrote:

On Sun, Sep 21, 2014 at 1:47 AM, Markus Sabadello <markus.sabadello@xdi.org> wrote:
We decided that in the XDI Bindings spec, we would define 1. how an XDI message can be posted directly to an XDI endpoint, and 2. how a browser-based POST-POST ("redirect"?) flow can be used. This is a prerequisite for defining the different scenarios of XDI connect requests.

What do we want to call these bindings, i.e. what are the "official names"?

1. XDI Direct POST Binding (or short: XDI Direct Binding)

I like both names.

I prefer XDI POST Binding (which we already have defined, essentially in the present HTTP Binding, right? or is this different in some manner)

2. XDI Browser POST-POST Binding (or short: XDI Browser Binding)

Again, I like both.

This is really just message proxying, right? using the browser as the proxy/forwarder… I would prefer to leave “browser” out, since that is just one kind of proxy/forwarder. lets see if we can define the generic mechanism, rather than a browser specific one. So I think it is more like “XDI Message Intermediaries” (and may, in fact, be transport binding agnostic). Since there are no doubt some browser specific requirements here, “XDI Browser Intermediary Binding” seems right to me.


We have also talked about an Artifact Resolve binding (from Andy's original Respect Connect spec), so maybe that's a third binding:

3. XDI Browser Artifact Resolve Binding (or short XDI Artifact Binding)

I like XDI Artifact Binding.

+1 for XDI Artifact Binding


Better ideas for naming these bindings?

Not from me. Others?


Peter Davis: Neustar, Inc.
Distinguished Engineer, Director, Neustar Foundry
45980 Center Oak Plaza Sterling, VA 20166

The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]