xdi message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [xdi] New approach to simple XDI HTTP/S REST API
- From: Markus Sabadello <markus.sabadello@xdi.org>
- To: Drummond Reed <drummond.reed@xdi.org>
- Date: Fri, 15 Feb 2013 17:08:06 +0100
Would this make the SimpleHttpRestApi obsolete, or would they co-exist at the same endpoint?
On the question of whether the messages should be just the pure query string, or an "xdi" query string parameter:
- First I felt that the pure query string option would be the more correct thing to do.
- Then I thought that this might cause conflicts with some _javascript_ libraries, but I did a few tests today (e.g. with the popular jQuery library), and I didn't find any problems.
- The query string parameter pattern is so common and I'm not sure if anyone is even still using query strings that don't have this pattern, so maybe that alone is a good reason why we should also do it that way.
So, not sure, let's discuss on the call..
Markus
On Fri, Feb 15, 2013 at 9:31 AM, Drummond Reed
<drummond.reed@xdi.org> wrote:
I'm putting this on the agenda for tomorrow's TC telecon, but wanted to call it out in so everyone had a chance to take a look:
It's a very simple approach to how to align the logical XDI graph operations with the HTTP/S protocol methods.
=Drummond
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]