Re: PEAR and PHPLib compatibility?
| From: | marko | Date: | Fri, 12 Mar 2004 14:17:21 +0000 |
| Subject: | Re: PEAR and PHPLib compatibility? | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-11259@lists.php.net to get a copy of this message | ||
Dear Lukas,
> Ah now we are getting closer to the real thing :-)
:)
> Well as I said in a previous mail in the next version of LiveUser we
> will probably storing of arbitrary user related data for each given user
> through the admin API and iirc we already support fetching if arbitrary
> data from the user table in the client part.
I didn't miss that.
> However it may be a bit clumsy to use the admin API if you plan to edit
> this data frequently. In LiveUser its more meant to be a way to store
> some additional information like email, icq number that doesnt change
> frequently.
But that would not be the case.
> For all other needs we will not provide the functionality as this goes
> beyond the scope of the package.
I was afraid of that answer. :)
> Dunno if this package may be what you are looking for:
> http://pear.php.net/package/Auth_PrefManager
Hmmm, I thought that package would do something similar to LiveUser...
Okay, I once more have a look at it.
> There are session handlers which also store in the database, but anyways
> this is a different topic since you are not talking about session
> variables :-)
:)
> PS: as you can see from all the needless emails it is really important
> to make sure you use the terms correctly. We could have saved us a fair
> number of mails if you wouldnt have called them "session variables".
I am sorry, Lukas. I am not a pro in programming and my terminology and my
English is certainly far from being sufficient for this kind of details.
It looks like. Sorry for that.
I really appreciate that you had the endurance to go with me through this
discussion!!! Now I have my questions really gotten answered. I am sorry
to have spoilt so much time of yours, I try to become more correct
terminology-wise in the future. :) That saves both of us time, I know.
Best regards and thanks again,
Marko