This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6416 - WS-Transfer/Enum - iterating over large resources
Summary: WS-Transfer/Enum - iterating over large resources
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-14 00:17 UTC by Doug Davis
Modified: 2009-03-12 00:25 UTC (History)
1 user (show)

See Also:


Attachments

Description Doug Davis 2009-01-14 00:17:46 UTC
WS-Transfer.get() will return the XML representation of a resource - 
however, what if the XML returned is just too large (either for the 
service or client) to deal with.  There needs to be a way for the client 
to iterate over the result - ie. pull back smaller pieces incrementally.

This might be possible today with WS-Transfer and WS-Enumeration however 
its not clear to me that is it - so if it is, I'd like to see some 
discussion of how to do this in one of the specs so that we have a 
well-known way to accomplish this that isn't service specific.  If this 
isn't possible today then I'd like to have the appropriate features added 
to one (both?) of the specs so that we can have an interoperable solution.

Its possible that using RT's fragment support is the way to do this - e.g. 
using xpath to pull back bits at a time - but I'm not sure that this is 
the best approach since it'll require the client to have intimate 
knowledge of the XML in advance.  It seems a more appropriate solution 
would be for the service to control which parts of the XML require 
cursors. 

Anyway, food for thought... :-)
Comment 1 Doug Davis 2009-01-16 11:18:29 UTC
Withdrawn