|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.
I prefer XDI POST Binding (which we already have defined, essentially in the present HTTP Binding, right? or is this different in some manner)
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.
+1 for XDI Artifact Binding
Distinguished Engineer, Director, Neustar Foundry
Peter Davis: Neustar, Inc.
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.