> On Mon, 2006-05-15 at 01:48 +0000, patrickdlogan wrote:
>> "Transport layer subdivides user-buffer into network-buffer sized
>> datagrams and enforces desired transmission control."
>>
>> So it appears safe to say that "transfer" means moving whole
>> application-specific information, while "transport" means moving bits
>> that make up some or all of that application-specific information as
>> best fits the network technology.
>
> Shouldn't chunking be taken as a something where the "Transport layer
> subdivides user-buffer into network-buffer sized datagrams and enforces
> desired transmission control."? HTTP 1.1 of course requires chunking
> support.
>
Hmmm, can you say a little more about why this is important to you? Are
you suggesting we should all use the word chunking or apportioning
responsibility for chunking at some particular layer or something else
entirely?
I'm a little confused by your statement "HTTP 1.1 of course requires
chunking support". HTTP 1.1 specifies a method of chunking which
clients and servers can use but that's separate from what, for example,
TCP/IP is doing underneath (it does fragmentation/re-assembly of packets
- never seen it called chunking).
Best,
Dan.
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
