From: | "Rick Gigger" <rick(at)alpinenetworking(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Randolf Richardson" <rr(at)8x(dot)ca> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL |
Date: | 2004-01-30 18:17:29 |
Message-ID: | 003901c3e75d$53922f90$0700a8c0@trogdor |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Randolf Richardson wrote:
> >>>In dealing with web applications and frontends to database or
> >>>even just a dynamic web site PHP has every bit the power and ability
that
> >>>Java does and the development time is way down.
> >>
> >>Uh, how about threads. I know that you don't need them much but it sure
> >>would be nice to be able to do background processing.
> >
> > [sNip]
> >
> > PHP doesn't support threads?
>
> Nope...
>
> I've always thought of Forking as
> > overkill where threads are light and elegant.
> >
>
> Depends on your environment... Forking in Linux is fairly lightweight.
But when you are using php with a web server you can't really use the
process contol functions safely. Forking apache processes on your own is
not a good idea. If forking were an option with php/apache it would do just
fine. But currently it is not a viable solution.
http://us2.php.net/manual/en/ref.pcntl.php (read the first paragraph)
From | Date | Subject | |
---|---|---|---|
Next Message | Rick Gigger | 2004-01-30 18:59:36 | Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL |
Previous Message | Jan Wieck | 2004-01-30 17:38:51 | Re: Pl/tcl auto-load problem |