> So, if you write a server implementation that maps an entire database as a > resource, and maps it to a URL, then yes, it is possible to consider a > database as a whole resource. Similarly, if you write a server > implementation that maps individual database cells to a resource, then > assigns each cell a distinct URL, then it is possible to consider > a database > cell as a Web resource. Although both these are possible, I've always thought that mapping rows to resources and tables to collections was the most useful. The MSDAIPP component used by MS clients (you can see its name in the User-Agent header if you sniff) takes this approach in a way: it presents an OLEDB interface to the client software developer which treats every file and collection as a row. lisaReceived on Wednesday, 18 July 2001 14:12:49 UTC
This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:23 UTC