Yasuo Ohgaki wrote:
> Marcus Börger wrote:
>> At 03:52 30.05.2002, Yasuo Ohgaki wrote:
>>
>> From my expirience postgres is slower if you use referential integrity
>> (what you should do)
>> but this you cannot do in mysql (and therefore it is some kind of data
>> storage but not a real rdbms).
At 03:52 30.05.2002, Yasuo Ohgaki wrote:
>Steve Meyers wrote:
>>Well, you didn't try it with MySQL, which is significantly faster than
>>Oracle and Postgres for most stuff. In any case, I agree that msession
>>is probably a better solution -- I just think that having built-in MySQL
>>session s
[EMAIL PROTECTED] wrote:
>> I agree that msession is better than using MySQL or PostgreSQL as a
>> session manager. However, most people who use PHP on web farms
>> already have some sort of database set up, so it seems logical to me
>> to be able to use it for storing sessions. MySQL actual
> [EMAIL PROTECTED] wrote:
>> The problem with using databases are they they are expensive and they
>> are slow.
>>
>> A generalized PostgreSQL session manager would be cool, I have
>> actually been thinking about such an extension. Using the schema from
>> the PG msession plugin, it would
[EMAIL PROTECTED] wrote:
> The problem with using databases are they they are expensive and they are
> slow.
>
> A generalized PostgreSQL session manager would be cool, I have actually
> been thinking about such an extension. Using the schema from the PG
> msession plugin, it would be fairly eas
> [EMAIL PROTECTED] wrote:
>
>>> At 10:20 25/05/2002 -0400, [EMAIL PROTECTED] wrote:
>>> >Marginalizing this capability IMHO is not the right direction, I
>>> >think there should, in fact, be a stronger push for this sort of
>>> >capability to be built in by default.
>>
>> Agree with that
[EMAIL PROTECTED] wrote:
>> At 10:20 25/05/2002 -0400, [EMAIL PROTECTED] wrote:
>> >Marginalizing this capability IMHO is not the right direction, I think
>> >there should, in fact, be a stronger push for this sort of capability to
>> >be built in by default.
>
> Agree with that too... but if so
> >These topics usually don't interest the average PHP developer - why
> >keep it in the same manual, then?
> >
> >What do you think about this?
> >
> +1 - Maybe even consider adding to part 2 some documentation on
> developing PHP itself. Right now, one must read the few files on the
> Zend API,
Hi,
> Let's make it a documentation problem, then:
> "Using PHP in web farms" or the like.
I'd like to make a suggestion here: What do you think of splitting up
the current PHP Manual into three major parts:
1. Developing in PHP ("for PHP users")
2. Extending PHP
3. PHP for System Admin
Hi,
> Chris Shiflett:
> The regular session implementation in PHP is extremely flexible, right?
> Sure, since you can write your own functions to do things such as store
> session data in a database, etc. However, there is *nothing* to help the
> average developer implement a professional-grad
At 10:20 25/05/2002 -0400, [EMAIL PROTECTED] wrote:
>I kind of went off in a huff yesterday with the whole PECL/pear issue with
>msession, it's over and lets move on. I did, however, want to explain *why*
>I think msession should be in the main code.
>
>In *big* websites, you need multiple web ser
I kind of went off in a huff yesterday with the whole PECL/pear issue with
msession, it's over and lets move on. I did, however, want to explain *why*
I think msession should be in the main code.
In *big* websites, you need multiple web servers serving copies of the same
data in a load ba
12 matches
Mail list logo
