Posted by Toby A Inkster on 04/16/07 17:35

amygdala wrote:

> Mind you, it's not a big issue, merely a cosmetic one. What I am still
> struggeling more with is the registrate function. Would you consider that a
> User class method. Or should it be in some other object. Or perhaps just be
> a regular function in the global script?

It could be implemented as a regular function, but I'd tend to put it as a
static factory function in the User class. (i.e. it returns the newly
registered User as an object -- much like the static login function
would.) This has the benefit of having internal consistency with the login
function. (A developer familiar with the login function would have little
trouble picking up the registration function.) Also, it keeps the function
"wrapped up" in the User class, so that everything is kept in one place.

--
Toby A Inkster BSc (Hons) ARCS
Contact Me ~ http://tobyinkster.co.uk/contact
Geek of ~ HTML/SQL/Perl/PHP/Python*/Apache/Linux

* = I'm getting there!

• Next in forum: Re: Can php control USB port on PC?
• Prev in forum: Re: Web Page Screenshot
• Thread view: Re: OOP database tables <-> php interface (semi LONG)

[Reply to this message]