|
|
Posted by ELINTPimp on 07/31/07 12:40
On Jul 30, 9:23 pm, "amygdala" <nore...@noreply.com> wrote:
> Hi all,
>
> I'm starting this new project in which I'ld like to implement sort of a
> design pattern I have seen being used in the CodeIgniter framework.
>
> Basically, the site will examine the URI and based on the segments of the
> URI it will fire up some controller class, for instance, say I have an inbox
> in which end-users can view messages they got from other users, they'ld
> start at:
>
> http://www.somesite.com/inbox/view/
>
> This will then call upon the function view in the class inbox:
>
> class Inbox extends Controller
> {
> // ...
> public function view()
> {
> // ...
> }
> // ...
>
> }
>
> Any trailing segments of the URI will be passed as supplement arguments to
> the function.
>
> Now, if $_POST variables are sent to some page and are needed by the called
> upon function in the appropriate class, would it be bad practice to simply
> extract those $_POST variables from the superglobal $_POST inside this
> function? Preferably I would like to send the $_POST variables as arguments
> to the function, but I'm not sure how to implement this correctly, nor am I
> even completely sure as to why this would be better practice, other than
> that the function will only accept predefined arguments.
>
> What are your views on implementing such a 'pattern' (if you will). Would
> you even suggest such an implementation, or am I bound to get into trouble
> with proposed pattern?
>
> Thank you in advance.
The request registry might be a good way to abstract the request data
in your case. The registry will handle the data gathering from your
superglobals (and possibly other places if you wish) and provide a
central point to references the data, without having to pass the
variables around your API.
http://www.phppatterns.com/docs/design/the_registry
Navigation:
[Reply to this message]
|