Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40306
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.44.28 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:mime-version:content-type
         :x-google-sender-auth;
        b=QoiwHoi2ZXJcv/WqTt5lfE9ikdS8h2UOo5R4/HimKSGP7x6p87C+fYKQeuv3lDr4wV
         Cn5XpcWk1SxKLQSGBEYkgYHqnYqFJQV4TGXCxcbVB5i/5Tyk9heDqzdp8jl0dzRav7Go
         uE7QYxbplR3QH/XY3I15+UkdZ3EnInZMWCm0w=
Message-ID: <d75889800809061519s5202a839q8837f43beb78ddd9@mail.gmail.com>
Date: Sun, 7 Sep 2008 03:49:04 +0530
Sender: prf.kishorekumar@gmail.com
To: "PHP Internals" <internals@lists.php.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_83814_32624330.1220739544334"
Subject: Strange problem with php_stream_read()
From: mangol.smith@gmail.com ("Mangol Smith")

------=_Part_83814_32624330.1220739544334
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello all,

I got a strange problem. I opened a network stream with my web server
(localhost:80) and wrote a HTTP GET into stream and reading the HTTP
RESPONSE.

buff =  (char *)emalloc(content_size);
php_stream_read(http_stream, buff, content_size);

where content_size is the Content-Length value in Response header. Problem
is that when I return RETURN_STRING(buff,1); to userland. I'm getting a
string with the content (response body) + some crap.

length of string is more than content_size.

for example: in a case content_size was 29; after php_stream_read() line,
the strlen(buff) is returning 41. How is this possible?

somewhere I read this

php_stream_read() differs from other stream read functions in one surprising
way. If the stream in use is not a plain files stream, only one call to the
underlying stream implementation's read function will be made, even if more
data was requested and more is actually available to return. This is a
compromise to let packet-based protocols such as UDP function cleanly
without blocking.

I didn't clearly understand its meaning. Does it has anything to do with my
results? Any help in understanding this behavious of php_stream_read() ?



--
Mangol Smith

------=_Part_83814_32624330.1220739544334--