Giovanni Giacobbi wrote:
>
> @William: I'm not sure I understand your reply: Apache#1 (the one running my
> test code) has nothing to do in all of this, because PHP is opening a raw
> socket and communicating on its own with Apache#2 (the one outputting the
> wsdl with chunked encoding). Thus P
On Sun, Jan 25, 2009 at 11:06:51PM +0100, Hannes Magnusson wrote:
>
> > > $opts = array('http' => array('method' => "GET", 'header' =>
> > "Accept-language: en\r\nConnection: close\r\n"));
> > $context = stream_context_create($opts);
> > stream_context_set_option($context, "http", "protocol_vers
Hi,
the recent email about pg_get_socket reminded me that PDO:PgSQL doesn't
have notify support. Here's a small patch and a phpt that add support
for the LISTEN/NOTIFY mechanism using PDO. The PDO::pgsqlGetNotify
method only returns an assoc array, but it could be easily modified to
mimic the beha
Hannes Magnusson wrote:
> On Sun, Jan 25, 2009 at 22:43, Giovanni Giacobbi
> wrote:
>> The problem turned out to be an invalid interpretation of the HTTP/1.1
>> protocol with "Transfer-Encoding: chunked" by the HTTP stream context, which
>> caused get_sdl() to parse a WSDL including the chunk t
Hello,
On Sun, Jan 25, 2009 at 4:24 PM, Lukas Kahwe Smith wrote:
>
> On 24.01.2009, at 19:19, Guilherme Blanco wrote:
>
>> Hi Oskar,
>>
>> Yes, you can use a plain array too.
>> I was just giving you a normal approach (ArrayAccess inherited class)
>> because you may want a special behavior under
On Sun, Jan 25, 2009 at 22:43, Giovanni Giacobbi wrote:
>
> The problem turned out to be an invalid interpretation of the HTTP/1.1
> protocol with "Transfer-Encoding: chunked" by the HTTP stream context, which
> caused get_sdl() to parse a WSDL including the chunk tags (hex numbers).
>
> Chunked
Greetings,
I recently upgraded to the latest PHP 5.3 snapshot and I found the following
SoapClient bug:
http://localhost/ws/catalog?wsdl";);
?>
Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL:
Couldn't load from 'http://localhost/ws/catalog?wsdl' : Start tag expecte
Hello all, and sorry for the massive cross-posting :)
As of now we have a list dedicated to Google Summer Of Code[1] discussions.
It is our hope that everyone who are interested in PHP and GSOC
subscribe[2] to the list and participate in the discussions, or just
lurk and follow the fun.
Among oth
Sean,
You make some very good points and I'll be the first to agree there is
definitely a room to improve the existing bug-tracker, in particular
its integration with the repository commits, but I do not think it
needs a fundamental rewrite. From what I can see most (I think its
all, but
On Sun, Jan 25, 2009 at 5:22 PM, Scott MacVicar wrote:
> On 25 Jan 2009, at 15:22, Lukas Kahwe Smith wrote:
>
>>
>> On 25.01.2009, at 16:17, Graham Kelly wrote:
>>
>>> Lastly, I really think all the PHP GSoC projects should be hosted in
>>> PHP's
>>> CVS under a central location (maybe something l
On 25 Jan 2009, at 15:22, Lukas Kahwe Smith wrote:
On 25.01.2009, at 16:17, Graham Kelly wrote:
Lastly, I really think all the PHP GSoC projects should be hosted
in PHP's
CVS under a central location (maybe something like
/repository/gsoc/2009/projectname/). It was very hard at times to
f
On 25 Jan 2009, at 16:12, David Zülke wrote:
Am 25.01.2009 um 14:29 schrieb Lukas Kahwe Smith:
On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most
importantly makes it easy to report and update bugs which is
conducive to more issues be
Am 25.01.2009 um 14:29 schrieb Lukas Kahwe Smith:
On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most importantly
makes it easy to report and update bugs which is conducive to more
issues being reported. Often extra features of bug track
On Sun, Jan 25, 2009 at 02:17:31PM +, ba...@barrycarlyon.co.uk wrote:
> In that case why wasn't this pointed out last year, and I could of done
> something more useful with my GSoC time last year..
http://markmail.org/message/daf4zi5dfktv7jjt
sean
signature.asc
Description: Dig
On 21.01.2009, at 22:05, David Grudl wrote:
Especially in namespaced code it should be very useful to have
"something" returning fully qualified name as string. It can be
operator, but I think introducing new keyword is bad way, or it can
be realized using well known magic constant in new
On 13.01.2009, at 16:58, Etienne Kneuss wrote:
Hello,
On Tue, Jan 13, 2009 at 4:43 PM, Mark van der Velden
wrote:
Hi list,
The following doesn't strike me as consistent behavior:
$a = new ArrayObject();
$a["foobar"] = NULL;
echo (int) isset( $a["foobar"] ); // Output: 1
Whil
On 24.01.2009, at 19:19, Guilherme Blanco wrote:
Hi Oskar,
Yes, you can use a plain array too.
I was just giving you a normal approach (ArrayAccess inherited class)
because you may want a special behavior under it too.
Forget SplObjectStorage docs they're outdated read the
source! =
On 25.01.2009, at 16:17, Graham Kelly wrote:
Lastly, I really think all the PHP GSoC projects should be hosted in
PHP's
CVS under a central location (maybe something like
/repository/gsoc/2009/projectname/). It was very hard at times to
find the
work done for other projects.
Actually if
Hi,
I think that there needs to be more feedback from the community on how
projects are going and the way they should go. This might help to curb some
of the problems being discussed where there was a gap between the project
and what the community wants. Feedback would also help the student know h
Stop top-posting.
On Sun, Jan 25, 2009 at 15:17, wrote:
> In that case why wasn't this pointed out last year, and I could of done
> something more useful with my GSoC time last year..
I did:
http://php.markmail.org/message/qfdvnpspq2tqpdqu?q=gsoc+list:net.php.lists.internals+from:%22Hannes
In that case why wasn't this pointed out last year, and I could of done
something more useful with my GSoC time last year..
On Sun, 25 Jan 2009 15:05:37 +0100, sean finney wrote:
> hi everyone,
>
> On Sat, Jan 24, 2009 at 11:40:08AM -0500, Ilia Alshanetsky wrote:
>> I think our bug current t
hi everyone,
On Sat, Jan 24, 2009 at 11:40:08AM -0500, Ilia Alshanetsky wrote:
> I think our bug current tracker is pretty good and most importantly
> makes it easy to report and update bugs which is conducive to more
> issues being reported. Often extra features of bug trackers make them
>
On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most importantly
makes it easy to report and update bugs which is conducive to more
issues being reported. Often extra features of bug trackers make
them overly complex to use and people jus
23 matches
Mail list logo
