We're developing a framework for handling large XML files between web-services. Each XML holds a list of entities representing our data, relevent to the specific user query. In the response there will be the SAME entity type and each response should be validated using a pre defined XSD.
Because the XML response can be quiet sizable we wanted to use a 'paging' mechanisem so that, for example, if the response should contains 6000 entities, we create 3 in-memory 'pages' and send only the first 2000 entities with a hash for the next page the user should ask for.
But then someone suggested we use the HTTP multipart specification, so I started reading and I think I understood how to use it but I didn't understand if the server response contain a whole body that I can validate by an XSD or is it like the 'chunked' response where the body just gets cut?
Thank you!
No comments:
Post a Comment