6416 2009-01-14 00:17:46 +0000 WS-Transfer/Enum - iterating over large resources 2009-03-12 00:25:46 +0000 1 1 1 Unclassified WS-Resource Access Transfer FPWD PC Windows XP CLOSED WONTFIX http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jan/0032.html P2 normal --- 1 dug dug bob public-ws-resource-access-notifications oldest_to_newest 23062 0 dug 2009-01-14 00:17:46 +0000 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... :-) 23144 1 dug 2009-01-16 11:18:29 +0000 Withdrawn