Posted by eliran on 09/09/07 18:34

On Sep 7, 11:19 pm, shimmyshack <matt.fa...@gmail.com> wrote:
> On Sep 7, 8:44 am, eliran <elira...@gmail.com> wrote:
>
>
>
> > On Sep 6, 8:10 pm, Michael Fesser <neti...@gmx.de> wrote:
>
> > > .oO(eliran)
>
> > > >I just wonder if in PHP there is some feature of internal database,
> > > >ofcourse with lock features to get/set data something like:
> > > >lock var1
> > > >$GLOBALS("var1")=varValue1
> > > >unlock var1
> > > >and on next request I can use the varValue1 like:
> > > >varValue1=$GLOBALS("var1")
>
> > > >is it hard to get ?
>
> > > >to use external files ,it's really not a resonable solution
>
> > > Why not? You have to keep the data somewhere. A file is one way for
> > > doing that. A database and shared memory (if available) are others.
>
> > > Micha
>
> > why PHP doesn't have some wrapper for keeping data
> > in the syntax I mentioned above like:
> > $GLOBALS("var1")=varValue1
> > so it will be kept as 'DataBase' for next request ?
> > so if it's a data base (memory or disk save)make:
> > ^$GLOBALS("var1")=varValue1 ; (with additional tag for 'disk')
> > no more
> > all the odbc,or flat file interfaces are not fast enough.
> > if I need to keep only some string or array elements.
>
> > EL
>
> you havent tried sessions with large amounts of data obviously.
> however a database is usually a flat file - with locking!!
> you can use memory but if the buck stops with you on a mission
> critical enterprise site give me a db over volatile memory everytime.
> the disk access on a raided scsi is negligible compared to network
> latency and rendering of the webpage, and other html flat files.
> just give it up and use sessions mate!!

as I have learned from this thread answers, I can keep values in
SESSION varaible ?
so even on different client requests I can get values I set before, no
matter
from what client is the request ?
or:
the SESSION usage is to handle the SESSION ID (of client)
and getting values PHP kept for this SESSION ID only ?

EL

[Back to original message]