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] HttpXdiMessagingBinding


Hello Markus, All,

here is the basics of a possible counterproposal (for now I've it only in my mind):

- one XDI operation per HTTP request/response (because all requests are sent to the same HTTP endpoint this does not introduce the overhead of establishing a new TCP connection)

- use HTTP verbs with their own semantics (GET,PUT,DELETE,...)

- use HTTP status codes with their own semantics (200 OK, 201 Created, 302 Found, 303 See Other, 307 Temporary Redirect, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found , 405 Method Not Allowed, 409 Conflict, 410 Gone, ...)

- use XRI translated into HTTP URI, as addressing. XRI segments are concatenated to the endpoint (see my proposal "Named Graphs, Named Links, Named Nodes" https://www.oasis-open.org/committees/download.php/41948/bartolomeo-Named%20Graphs%2C%20Named%20Nodes%2C%20Named%20Links%20%28camera%20ready%29.pdf)

- use HTTP Etags and other cache controls to improve performance (allowing a client to issue conditional requests)

- this comes for free: take advantage of the world-wide content delivery infrastructure designed for HTTP

What do you think?

Giovanni


Def. Quota Markus Sabadello <markus.sabadello@xdi.org>:

Hmm I think the idea behind not relying too deeply on specific HTTP
features was that XDI should allow bindings to several different protocols,
and should still always work kind of the same way.

Anyway, Bill what is the process if one TC member disagrees with a proposal?
He would have to write a counter-proposal, right? :)

Markus

On Tue, Jul 3, 2012 at 1:00 PM, Giovanni Bartolomeo <
giovanni.bartolomeo@uniroma2.it> wrote:

Hello,

Whereas I like very much the idea of an HTTP binding for XDI (thanks
Markus for having started this page), I have to express my concern on the
choice of remaining formally compliant with it without really relying on
its already provided semantics.

I would be in favour of a deeper integration, especially now that
developers seem finally to have re-discovered (http://programmableweb.com)
the unifying power of REST, that, as often Bill has pointed out, is much
more than CRUD.

I think we should take more advantages of functional (e.g., addressing,
methods, error codes, eTags, etc.) and non functional (e.g., caching)
capabilities already offered by the protocol, instead of duplicating this
functions on top of it.

NOTE: I'm not saying that XDI should totally rely on HTTP. I'm saying
that, where HTTP (or another protocol) already provides these functions, it
would be a pity to replicate them on top of it, rather than proceed with a
mapping.

Sorry to be once more not aligned with the position of the TC members :)

Thanks,
Giovanni


Def. Quota Drummond Reed <drummond.reed@xdi.org>:


 Markus, good job on this. I added a sentence to the "Out of Scope" section
to clarify that the questions/issues listed there are out-of-scope for
this
proposal but should be dealt with in other proposals.

Everything else looks good to me.

I encourage everyone else to review it -- unless there are any objections,
we will approve this proposal on this Friday's telecon.

=Drummond

On Sat, Jun 30, 2012 at 4:29 AM, Markus Sabadello
<markus.sabadello@xdi.org>**wrote:

 I updated this page according to what we talked about during the TC call,
please review.
https://wiki.oasis-open.org/**xdi/HttpXdiMessagingBinding<https://wiki.oasis-open.org/xdi/HttpXdiMessagingBinding>

Markus






------------------------------**------------------------------**----
Invito da parte dell'Ateneo:
Il tuo futuro e quello della Ricerca Scientifica hanno bisogno del
tuo aiuto. Dona il  5 x mille all'Universita' di Roma Tor Vergata
codice fiscale: 80213750583 http://5x1000.uniroma2.it



------------------------------**------------------------------**---------
To unsubscribe, e-mail: xdi-unsubscribe@lists.oasis-**open.org<xdi-unsubscribe@lists.oasis-open.org>
For additional commands, e-mail: xdi-help@lists.oasis-open.org






----------------------------------------------------------------
Invito da parte dell'Ateneo:
Il tuo futuro e quello della Ricerca Scientifica hanno bisogno del
tuo aiuto. Dona il  5 x mille all'Universita' di Roma Tor Vergata
codice fiscale: 80213750583 http://5x1000.uniroma2.it




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