- From: Mark Baker <distobj@acm.org>
- Date: Tue, 4 Mar 2003 12:49:31 -0500
- To: "Burdett, David" <david.burdett@commerceone.com>
- Cc: www-ws-arch@w3.org
On Tue, Mar 04, 2003 at 08:43:19AM -0800, Burdett, David wrote: > AEROSPACE > For legal reasons, when an aeroplane is sold, the Invoice must be > accompanied by a line by line parts breakdown including serial numbers. > Given that there can be millions of parts in a commercial aeroplane, the > estimated maximum message size can be up to 2GB. Wow! > TELECOMMUNICATIONS > Perhaps there aren't enough aeroplanes sold to make it worthwhile developing > an approach to just meet their needs, so how about this example from the > telecomms industry ... A major telecommunications company wants to provide > an itemised Invoice detailing each call for a company with hundreds of > locations. Sometimes there can be 100k+ line items. As each line is > approximately 90 characters long (including tags), messages sizes can be > easily over 10Mb or more. > > Typically, the way to handle this is to have a "utility protocol" to break > up the message into smaller chunks prior to sending and then re-assemble at > the far end. > > Do we want to include this type of requirement in our thinking? Also how > well would this sort of problem be handled by a REST approach, without any > additional work? HTTP chunking? Without any more detail, it seems to be what you're looking for. FWIW, HTTP byte ranges are pretty useful for large transfers too, as it allows for resumption of partially completed transfers. MB -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Web architecture consulting, technical reports, evaluation & analysis
Received on Tuesday, 4 March 2003 12:46:16 UTC