Re: Package proposal: Unique
| From: | cagrET | Date: | Wed, 25 Jun 2003 20:40:55 +0000 |
| Subject: | Re: Package proposal: Unique | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17729@lists.php.net to get a copy of this message | ||
> Yes, I'm sure. You *never* call Unique::instance() and thus cannot set the
> static variable within it.
> Here is another fun part from factory():
> [php]
> $this->Db = new Unique;
> [/php]
> This will probably *overwrite* DB's instance. Not sure as I didn't run
this, but
> still...
factory() method is called only once
and after calling factory() $instance will contain Unique object
if u dont see that, its your problem :)
> The benchmarks clearly show that you'd be better using native MySQL
functions. :]
yeah, sure :)
u can also code your web applications in C ... :)
> > it has dedbugging queries / error handling features that fit my needs,
> > what is wrong with that ?
> Nothing is wrong with that. :]
great !
> > okay so could u explain me, how this should be done ?
> > thx for help
> Dunno. Last time I implemented this, I just stored the tokens in session.
Thus
> no need to access database, no need to do separate GC...
sounds like a good idea
but is sessiondata locked ?
i mean when user clicks few times on "submit" button
so the 2nd request/click will wait until 1st is executed ?
they use the same session
adding uniq_id to sessiondata in 1st execute, will be seen in 2nd execute ?