<snip>
In the client:
customers.get("http://my.customer.database.com/customers/1234";);
returns an instance of the Customer XSD complex type
customers.put("http://my.customer.database.com/customers/1234";,
customerDataObject) updates customer 1234 with a Customer instance.
customers.get("http://my.customer.database.com/customers/";) returns a
list of URIs to the customers.
On the server, the CustomerResource component implements the Customer
resource management verbs:
class CustomerResource {
DataObject get(string uri);
void post(string uri, DataObject customer);
void put(string uri, DataObject customer);
void delete(string uri);
list<string> list(string uris);
}
Also, I was thinking that somehow our REST work should tie in with the
DAS work that we're doing in Tuscany.
Thoughts?
<snip>
I have spent a little time thinking about DAS and REST ... no epiphany
so far. Some RDB vendors offer URL access to relational data with an
option to return results as xml with something like this:
http://localhost/myDatabase?sql=SELECT+firstname,lastname+FROM+employees+FOR+XML+AUTO
So, this seems quasi-restful although what is returned is really the
results of a query rather than a resource. I suppose this would be more
restful and similar to Sebastien's example if the get returned a list of
urls of Employees that satisfied the query.
I am not sure we would want to embed SQL in the URL but it also does not
seem to make much sense to invent a new query language. Without a
fairly sophisticated query language, how could a client retrieve a graph
of results like: Customers-Orders-LineItems? I am starting to ramble.
I need to think about this a bit more.
--Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
