> 4. Include an opcode cache by default. A lot of work has gone into
>pecl/apc recently, but I am not hung up on which one goes in.
I have no karma to +1, but would if I could. It would be wonderful if
something like xdebug could profile with op code cache on as well,
should it be possible. :
On 8/12/05, Brian J. France <[EMAIL PROTECTED]> wrote:
> I see the code for SO_LINGER in apr_socket_opt_set, but I don't see any
> place in the server code that calls apr_socket_opt_set with
> APR_SO_LINGER.
I stand corrected. I should have used gdb and tested that before I
posted. So they put cod
Has the upload progress patch been ever been voted up or down?
-steve--
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 8/12/05, Brian J. France <[EMAIL PROTECTED]> wrote:
> Really? We just did a around of discussion/debugging on this at work
> and I found that it uses ap_lingering_close which is like the
> lingering_close function in 1.3.
:)
Yes, it does do ap_lingering_close, and it sets SO_LINGER. I have no
srclib/apr/network_io/unix/sockopt.c:if
(setsockopt(sock->socketdes, SOL_SOCKET, SO_LINGER, (char *) &li,
sizeof(struct linger)) == -1)
...
It gets set if APR_SO_LINGER, is set which it is:
srclib/apr/include/apr_network_io.h:#define APR_SO_LINGER1
/**< Linger */
and if
Yes, you are quite correct in that a very large site (Yahoo, Google,
etc) will use a caching ISP (aka Akami). In fact, I imagine that it
would be a completely separate domain name so there would be no
cookies and everyone down the chain can easily cache the content as
well. Doesn't work for all obj
Yes, thanks! Hopefully by next week I'll have learned how to set
FastCGI up securely and with a php opcode accelerator active. Then
I'll give it some time and return with results.
On 8/11/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> Hi Steve,
>
> Will be interested to see your results. As I ment
Just a couple last notes on lingering:
o Apache 2+ uses SO_LINGER by default if it defined for that system.
Apache 1 will only use it if you define USE_SO_LINGER (I suppose in
configure). Apache2 has all sorts of stuff in the comments of the code
and in the manual which is just wrong. Its all fro
On 8/9/05, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> PHP by default compiles as a non-pic shared library now which is just as
> fast as a static build inside Apache since it is the pic stuff that
> slows down a DSO. So there is really no need for static builds anymore,
> unless you happen to be
That is great to know. In that case, I won't worry about threading
again. I'm assuming that the 4.3.0 Release Announcement that FastCGI
was removed is bogus or reversed.
Unfortunately my source for mysql connection pooling was never
upgraded to support 4.1's APIs. If anyone knows one, pass it by m
On 8/9/05, Andreas Korthaus <[EMAIL PROTECTED]> wrote:
> By using lighttpd with fastcgi we seperate the webserver process from
> php processes (which could even work on other machines)...
Someone else emailed me about using FastCGI with Apache 2.1/event but
I just figured that there would be a sig
On 8/9/05, steve roussey <[EMAIL PROTECTED]> wrote:
> > My stuff is far bigger and busier than yours
>
> My spewing of stuff...
I often write things to make me feel better and delete them before
hitting send. Sort of stream of consciousness that I edit before
sending. IRas
On 8/8/05, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> > 3. Problems with thread-safety of modules
>
> You missed the most serious one. Thread safety problems in random
> libraries you link in and we have absolutely no control over those.
OK, I am confused. I always thought (an assumption with n
I work at a company with a high volume web site (you know the drill:
LVS directors managing a farm of webservers (with php accelerators) to
a few database servers (MySQL if you want to know -- anyone happen to
have experience with Emic clustering for MySQL, btw? OK, back on
topic...)
PHP4 and Apac
14 matches
Mail list logo
