paulruizendaal wrote:

>>nice package, I know a couple of people I might be able to persuade
>>to try fbird+php with this :-)
>
>
> Thanks. Spread the word, I would say :^)
>
> For the 1.0 release we still need to add a simple sample database in
> the examples section, perhaps with a nice php/ajax page to
> view/insert/delete records from a single sample table, focusing on
> slick looks. Eye candy sells.
>
> Who wants to help with this?

problem is that slick and simple are kind of mutually exclusive,
other thing to consider is that most of what firebird great are
the rather advanced features like computed fields, triggers, events,
etc which are difficult to put accross (visually) in a [simple] webbased
demo.

I have a non-ajax framework that is slick, but not simple (then
again its totally generic...) - I wrote it with Ard (from ibase extension
fame) which might be interesting to use.

>
>
>>I notice that the webserver you use is a threaded beast, which
>>seems like it will cause subtle/strange problems if php is used
>>with certain (not threadsafe) extensions - and nobody really knows
>>which they are (although the engine itself should be thread safe,
>>nobody recommends using it and most of the core development
>>guys _will_not_ use php in a threaded env...
>>
>>how does this affect you/phpserver?
>
>
> I does not -- at least I think it doesn't
>
> The webserver is threaded, but talks to php running in a separate
> process. Communications are by way of fastcgi ("php -b"). The php
> fastcgi server process is single threaded, afaik. If the php process
> dies or becomes unresponsive, the webserver simply kills it and
> restarts a new php fastcgi server process.

ok, I never really understood the fast cgi wotsit. thanks for the
info!

does using fastcgi limit stuff like sessions, server env vars etc?
in the same way that using php as a cgi with apache sucks compared
to using it as a module?

>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>