Ad:

PHP Discussion Thread
Unsolved
Views: 2038

Page 1
2
Next

You are currently viewing page 1 of this multi-page discussion thread

Jul 9th, 2009

Using GET, POST, REQUEST in OOP

Expand Post »

Hi all. I have a current PHP script which checks a number of GET, POST, and REQUEST variables. These are currently in a top-down PHP file and these variables control the flow of the application. I want to convert file to a PHP class, create an object and then access the class functions to perform actions in my application. I'm wondering are there any problems with creating a PHP like this:

PHP Syntax (Toggle Plain Text)
class foo {
    function __ construct() {
    }
    function fooBar() {
        if($GET['param1'])
            return 1;
        return 0;
    }
};
 
$obj = new foo();
class foo {
    function __ construct() {
    }
    function fooBar() {
        if($GET['param1'])
            return 1;
        return 0;
    }
};

$obj = new foo();

And then in my other documents I can just check the value of fooBar via:

PHP Syntax (Toggle Plain Text)
<?php if(fooBar()) {....} ?>
<?php if(fooBar()) {....} ?>

Now this isn't exactly what I'm trying to do but it illustrates it. Is this good? i.e. proper practice? If not, how can I accomplish what I'm trying to do.

Thanks.

Last edited by Barefootsanders; Jul 9th, 2009 at 6:59 pm.

Similar Threads

Create a post request programmatically in ASP.NET in C#
HTTP GET and POST REQUEST in Java
Post Bulk Data In AJAX request in JavaScript / DHTML / AJAX
A PHP REST POST request? in PHP
Sending a post request through url in Java

Barefootsanders

Reputation Points: 10

Solved Threads: 3

Junior Poster

Offline

165 posts
since Oct 2006

Permalink

Jul 9th, 2009

Re: Using GET, POST, REQUEST in OOP

Those are called superglobals and they will work inside a class. Also the way you called the method in the if statement is incorrect. I hope you know that.

FYI: _POST and _GET are part of _REQUEST. Make sure you use the specific request type. Using _REQUEST isn't the best thing to do.

kkeith29

Reputation Points: 235

Solved Threads: 193

Nearly a Posting Virtuoso

Offline

1,315 posts
since Jun 2007

Permalink

Jul 9th, 2009

Re: Using GET, POST, REQUEST in OOP

Click to Expand / Collapse Quote originally posted by kkeith29 ...

Those are called superglobals and they will work inside a class. Also the way you called the method in the if statement is incorrect. I hope you know that.

FYI: _POST and _GET are part of _REQUEST. Make sure you use the specific request type. Using _REQUEST isn't the best thing to do.

Thanks for the response. How can I use them then? I'm going to assume pass them in as parameters? The only problem with that is that my program relies on $_GET and $_POST for program flow. What I'd have to do is pass them in before the HTML starts to set them and then just check them. Does that sound right?
And yes, I know the if syntax isnt correct.. Just threw up a quick example. Thanks though!

Barefootsanders

Reputation Points: 10

Solved Threads: 3

Junior Poster

Offline

165 posts
since Oct 2006

Permalink

Jul 9th, 2009

Re: Using GET, POST, REQUEST in OOP

You do not have to pass them as params. They can be used anywhere. Your example will work just fine.

kkeith29

Reputation Points: 235

Solved Threads: 193

Nearly a Posting Virtuoso

Offline

1,315 posts
since Jun 2007

Permalink

Jul 9th, 2009

Re: Using GET, POST, REQUEST in OOP

Click to Expand / Collapse Quote originally posted by kkeith29 ...

You do not have to pass them as params. They can be used anywhere. Your example will work just fine.

O wow, sorry. I read your previous post wrong.

Thanks!

Barefootsanders

Reputation Points: 10

Solved Threads: 3

Junior Poster

Offline

165 posts
since Oct 2006

Permalink

Jul 9th, 2009

Re: Using GET, POST, REQUEST in OOP

As was noted before, they are superglobals, you can use them anywhere. However, I suggest that you don't. If you're going to go the OOP route then I would suggest abstracting dealing with GET/POST/COOKIE/SESSION variables to a class that deals with them specifically called Request or something along those lines that can appropriately sanitize/parse/etc.

ShawnCplus

Sponsor

Reputation Points: 520

Solved Threads: 268

Code Monkey

Offline

1,564 posts
since Apr 2005

Permalink

Jul 9th, 2009

Re: Using GET, POST, REQUEST in OOP

Click to Expand / Collapse Quote originally posted by ShawnCplus ...

As was noted before, they are superglobals, you can use them anywhere. However, I suggest that you don't. If you're going to go the OOP route then I would suggest abstracting dealing with GET/POST/COOKIE/SESSION variables to a class that deals with them specifically called Request or something along those lines that can appropriately sanitize/parse/etc.

Abstraction is one thing I'm not too advanced with.. Could you provide an example of what you mean by an abstraction layer using the GET/POST/etc... variables? Any help would be appreciated.

Thanks.

Barefootsanders

Reputation Points: 10

Solved Threads: 3

Junior Poster

Offline

165 posts
since Oct 2006

Permalink

Jul 10th, 2009

Re: Using GET, POST, REQUEST in OOP

I'll give you a pretty advanced example for the sole reason for you to learn from.

php Syntax (Toggle Plain Text)
<?php
class Request
{
  const TYPE_NONE   = 0;
  const TYPE_ALPHA  = 1;
  const TYPE_DIGIT  = 2;
  const TYPE_ALNUM  = 3;
 
  const GET         = 10;
  const POST        = 11;
  const COOKIE      = 12;
  const SESSION     = 13;
 
  public static function get($name, $method = null, $validation = null)
  {
    if ($method < self::GET && $validation === null) {
      $validation = $method;
      $method = self::GET;
    } else if ($method === null ) {
      $method = self::GET;
    }
 
    if ($validation === null) {
      $validation = self::TYPE_NONE;
    }
 
    $holder = null;
    switch ($method) {
      case self::GET:
        $holder = $_GET;
        break;
      case self::POST:
        $holder = $_POST;
        break;
      case self::COOKIE:
        $holder = $_COOKIE;
        break;
      case self::SESSION:
        $holder = $_SESSION;
        break;
    }
 
    if (!isset($holder[$name])) {
      return false;
    }
 
    $validator = null;
    switch ($validation) {
      case self::TYPE_ALNUM:
        $validator = 'alnum';
        break;
      case self::TYPE_DIGIT:
        $validator = 'digit';
        break;
      case self::TYPE_ALPHA:
        $validator = 'alpha';
        break;
    }
 
    $ret_val = $holder[$name];
    $valid_func = 'ctype_' . $validator;
    return (($validator === null) ? $ret_val : (( $valid_func($ret_val) ) ? $ret_val : null ) );
  }
}
<?php
class Request
{
  const TYPE_NONE   = 0;
  const TYPE_ALPHA  = 1;
  const TYPE_DIGIT  = 2;
  const TYPE_ALNUM  = 3;

  const GET         = 10;
  const POST        = 11;
  const COOKIE      = 12;
  const SESSION     = 13;

  public static function get($name, $method = null, $validation = null)
  {
    if ($method < self::GET && $validation === null) {
      $validation = $method;
      $method = self::GET;
    } else if ($method === null ) {
      $method = self::GET;
    }

    if ($validation === null) {
      $validation = self::TYPE_NONE;
    }

    $holder = null;
    switch ($method) {
      case self::GET:
        $holder = $_GET;
        break;
      case self::POST:
        $holder = $_POST;
        break;
      case self::COOKIE:
        $holder = $_COOKIE;
        break;
      case self::SESSION:
        $holder = $_SESSION;
        break;
    }

    if (!isset($holder[$name])) {
      return false;
    }

    $validator = null;
    switch ($validation) {
      case self::TYPE_ALNUM:
        $validator = 'alnum';
        break;
      case self::TYPE_DIGIT:
        $validator = 'digit';
        break;
      case self::TYPE_ALPHA:
        $validator = 'alpha';
        break;
    }

    $ret_val = $holder[$name];
    $valid_func = 'ctype_' . $validator;
    return (($validator === null) ? $ret_val : (( $valid_func($ret_val) ) ? $ret_val : null ) );
  }
}

USAGE:

php Syntax (Toggle Plain Text)
// basic GET param with no validation
$blah = Request::get('blah');
// GET param with validation
$blah = Request::get('blah', Request::TYPE_DIGIT);
// POST param
$blah = Request::get('blah', Request::POST);
// POST param with validation
$blah = Request::get('blah', Request::POST, Request::TYPE_ALNUM);
// basic GET param with no validation
$blah = Request::get('blah');
// GET param with validation
$blah = Request::get('blah', Request::TYPE_DIGIT);
// POST param
$blah = Request::get('blah', Request::POST);
// POST param with validation
$blah = Request::get('blah', Request::POST, Request::TYPE_ALNUM);

Now, given that PHP 5.3 has been released I could've gotten REALLY fancy and allowed the $validation parameter to be a lambda callback (I'm running 5.3 so I could've but I HIGHLY doubt you are so I didn't)

Last edited by ShawnCplus; Jul 10th, 2009 at 12:37 am.

ShawnCplus

Sponsor

Reputation Points: 520

Solved Threads: 268

Code Monkey

Offline

1,564 posts
since Apr 2005

Permalink

Jul 10th, 2009

Re: Using GET, POST, REQUEST in OOP

Wow thanks so much for that. I thought you meant an actual abstract class, i.e:

PHP Syntax (Toggle Plain Text)
abstract class foo {...}
abstract class foo {...}

One question though.. is there any significance behind the values of the constants or did you just arbitrarily pick them?

Thanks again.

Last edited by Barefootsanders; Jul 10th, 2009 at 10:15 pm.

Barefootsanders

Reputation Points: 10

Solved Threads: 3

Junior Poster

Offline

165 posts
since Oct 2006

Permalink

Jul 10th, 2009

Re: Using GET, POST, REQUEST in OOP

Click to Expand / Collapse Quote originally posted by Barefootsanders ...

Wow thanks so much for that. I thought you meant an actual abstract class, i.e:
PHP Syntax (Toggle Plain Text)
abstract class foo {...}
abstract class foo {...}
One question though.. is there any significance behind the values of the constants or did you just arbitrarily pick them?

Thanks again.

Well, arbitrary in the sense that they aren't language constants but I picked the names because their purpose is easy to determine.

ShawnCplus

Sponsor

Reputation Points: 520

Solved Threads: 268

Code Monkey

Offline

1,564 posts
since Apr 2005

Page 1
2
Next

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.

Previous Thread in PHP Forum Timeline: Problem with mysql error...

Next Thread in PHP Forum Timeline: Php my admin for reporting

DaniWeb Message

Cancel Changes

User Name
Password