- From: Janne Saarela <janne.saarela@profium.com>
- Date: Wed, 16 Jun 2004 12:56:59 +0300
- To: "Seaborne, Andy" <andy.seaborne@hp.com>
- Cc: Jim Hendler <hendler@cs.umd.edu>, RDF Data Access Working Group <public-rdf-dawg@w3.org>
I posed quick question yesterday regarding the programming model behind this streamable protocol suggestion. I am also eager to hear more information about ODBC/JDBC experiences that someone (Jim?) promised to elaborate by email. I wish to understand how an ordinary Java/C# programmer could use familiar constructs such as ResultSets in managing the streaming results. Once I understand this better, I am ready to discuss about the adoption of this requirement. Janne > A streamable protocol does not require the client to call for more results. > No flow control at this level - adding flow control (over what TCP has - > that that is very clever and highly tuned) is a lot of work for DAWG and a > lot of work for implementers. > > A streamable protocol requires the encoding to be in a an order so that > results can be extracted without needing to see the end of results, or, more > usually, all of one result possibility is encodes before starting the > second. -- Janne Saarela <janne.saarela at profium.com> Profium, Lars Sonckin kaari 12, 02600 Espoo, Finland Internet: http://www.profium.com
Received on Wednesday, 16 June 2004 05:57:01 UTC