Thank you both of you. For your information we evolved in our use case so in our design : we first make a "selection" (through a kind of search if required) of a given item on the first resource, and make a search on the second resource with the selected items as additional filtering criterias. To say it differently, with different providers, we cascade the queries. We achieve 'jointures' only 'inside' one given resource provider.
It does change the use case, definitely; but in our case it's satisfying to acheive the overall business process. Concerning "web join" on large resources, perhaps we can imagine a query system coupled to an indexing system, similarly to current web search engines: aka building asynchronously a local "extract" of remote ressource providers and making the join query using local "data indexes" instead of on-the-fly web resources ? For discussion only... -- View this message in context: http://n2.nabble.com/rest-practice-how-do-you-join-linked-resources-from-2-providers-tp4651158p4708078.html Sent from the Restlet Discuss mailing list archive at Nabble.com. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2457509
