W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > April to June 2004

Re: Streamability II

From: Janne Saarela <janne.saarela@profium.com>
Date: Tue, 22 Jun 2004 11:41:28 +0300
Message-ID: <40D7F0B8.4060800@profium.com>
To: Tom Adams <tom@tucanatech.com>
Cc: public-rdf-dawg@w3.org

Hi Tom

> As promised, for those concerned about implementability, here is an 
> outline from one of our engineers of our approach to streaming results 
> across the wire:
>
> "When a remote query is performed, the ResultSet is wrapped in a paging 
> class that can return a page of results at a time. On the client side is 
> a class that meets the ResultSet interface and calls across the network 
> to this paging class. When this client-side ResultSet class is returned 
> from a query it contains its first page. Iterating over the client-side 
> ResultSet just iterates over the results in the internal page. Once a 
> page is finished, the next page is automatically requested from the 
> paging class on the server and iterating can continue."

Isn't this effectively an approach that stores the state for each 
individual client on the server side? I would agree with Andy's
comment in

http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0606.html

where the requirement to store state for each client is
considered an unnecessary burden.

Have I understood correctly your concept of a 'paging class'?

Janne
-- 
Janne Saarela <janne.saarela at profium.com>
Profium, Lars Sonckin kaari 12, 02600 Espoo, Finland
Internet: http://www.profium.com
Received on Tuesday, 22 June 2004 05:00:10 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:19 GMT