Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of adam.kocoloski@gmail.com
 designates 209.85.221.203 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:cc:message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=DW9yxGc2TdLPfYe8Iizu4vI/PMsPb0Ahk0WVJrI+kM1wn86TvwCNipOitvxUhp7quC
         5TCfBagfdu4Hwa+ZXmUHrPLtEjjqXgOmp/F5MIGrt1sa7tpFBcQ4005zTfglIXAu8Bux
         H2JWWNwrK/mAFKOOVAb5Y4nO9O7GEbg55u1VE=
Sender: Adam Kocoloski <adam.kocoloski@gmail.com>
Cc: Darrell Huang <jinhuang@memego.com>
Message-Id: <9429F4DE-6DB6-4516-A1F0-3B7E4FE4F6D6@apache.org>
From: Adam Kocoloski <kocolosk@apache.org>
To: user@couchdb.apache.org
In-Reply-To: <20090526075927.GA9381@uk.tiscali.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: I need to know how to parse attachment data
Date: Tue, 26 May 2009 09:57:15 -0400
References: <BE5FDD8E38484950980325DD1C0D2E40@Darrell>
 <20090526075927.GA9381@uk.tiscali.com>

On May 26, 2009, at 3:59 AM, Brian Candler wrote:

> On Mon, May 25, 2009 at 12:07:55PM +0800, Darrell Huang wrote:
>> Hi, everyone, I got some trouble in reading the attachment data from
>> documents with the HTTP API. When an attachment is downloaded with  
>> the
>> API, some extra data is found before and after the attachment data,  
>> and
>> the data can be different at different times.
>> For example, when I downloaded an attachment with the jpg format  
>> several
>> weeks ago, there is a character sequence "dbc\r\n" preceding the  
>> actual
>> file data, but when I did that today, it was "a24\r\n".
>
> That would be HTTP chunking, wouldn't it? If you send a request  
> advertising
> HTTP/1.1 capability, then you are required to accept
> Transfer-Encoding: Chunked
> in the response.
>
> Regards,
>
> Brian.

Yep, and those character sequences are hex representations of the  
length of the chunk.

Adam