Sebastian wrote:
The PHP soap implementation is very fast by the way ... my benchmarks
indicated 3-4ms request times on the LAN (without doing anything useful
inside the request). This compares to over 30ms for the
mod_perl/Soap::Lite implementation (and I haven't tested Java or .Net)
Can
> The PHP soap implementation is very fast by the way ... my benchmarks
> indicated 3-4ms request times on the LAN (without doing anything useful
> inside the request). This compares to over 30ms for the
> mod_perl/Soap::Lite implementation (and I haven't tested Java or .Net)
Can you provide code
steve wrote:
Personally, I wouldn't mind connection pooling too. I like to dream...
And where would such a pool live?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
The problem isn't the duration of the soap query call, it's how long
to wait before giving up on establishing the connection. The connect
timeout is completely independent from the soap call duration or the
work that it performs.
--Wez.
On 12/21/05, steve <[EMAIL PROTECTED]> wrote:
> > There's n
On 12/21/05, Andreas Schiffler <[EMAIL PROTECTED]> wrote:
> >There's not much difference between .25 and 1 second.
> Ah, this may be so for the traditional use of webservices. But for
> eCommerce applications for example speed is king and its also very
> important to provide consistent speeds (i.e.
> There's not much difference between .25 and 1 second.
Actually, there is. It depends on the length of time of a typical page
request (and the proportion of the delay to the typical time), and the
hardware setup to handle that. The 4x slowdown can cause a cascade
effect as it might cause more tha
Wez,
There's not much difference between .25 and 1 second.
Ah, this may be so for the traditional use of webservices. But for
eCommerce applications for example speed is king and its also very
important to provide consistent speeds (i.e. not hang). I don't have
published reference links on
There's not much difference between .25 and 1 second.
If you're talking soap on each page render, you're probably doing
something wrong anyway; you should have some kind of cache in your web
app.
That's not to say that we won't fix this issue, but we're not in a
rush to do so.
If you're feeling mo
Hi all,
I am new to php source code hacking, but got into it for a particular
reason: I need sub-second SOAP request timeouts.
To qualify the reasoning behind this sub-second timeout requirement a
bit further, let me explain what it is used for: We are implementing a
system that changes webc
