In their continuing series on creating an email application in PHP, DevShed has posted this new article showing how to create folders for the application, letting you sort and store the messages easily.

In this article, the fourth and final one of our series covering the creation of a PHP email application, we are going to look at the code for some of the remaining pages of the mail application. Chief among these is the NewMsg.php page, which is where items, to be more precise, new messages, are either saved as drafts or saved as sent messages.

They give the code to display the message, including its location, before getting on to the form handling script for the results. There's some extra code included in this handling functionality, so they finish up by explaining what those sections do and how to add on one more folder - the Trash.

In their continuing series on creating an email application in PHP, DevShed has posted this new article showing how to create folders for the application, letting you sort and store the messages easily.

In this article, the fourth and final one of our series covering the creation of a PHP email application, we are going to look at the code for some of the remaining pages of the mail application. Chief among these is the NewMsg.php page, which is where items, to be more precise, new messages, are either saved as drafts or saved as sent messages.

They give the code to display the message, including its location, before getting on to the form handling script for the results. There's some extra code included in this handling functionality, so they finish up by explaining what those sections do and how to add on one more folder - the Trash.

On Chris Shiflett's blog, there's a post that looks a an issue that's been brought up on the New York PHP mailing list concerning two variables in the $_SERVER superglobal - SERVER_NAME and HTTP_POST.

The question initially was "arean't these the same thing?" Chris answers:

There were several informative replies within the first few minutes, but there's more to this question than most people realize. In fact, I'm reminded of a blog entry from Zeev last year, where he warns against $_SERVER['SERVER_NAME'].

Zeev suggests that SERVER_NAME is pulled from the Host header from the remote user. Chris reminds us, also, of some disagreements with this view Zeev presented, namely from Rasmus. Chris then gives an example script to illustrate hos things area really handled - the variables use the given values when they're present in the request, but they still do default back to the ServerName when absent (so only in certain circumstances).

On Chris Shiflett's blog, there's a post that looks a an issue that's been brought up on the New York PHP mailing list concerning two variables in the $_SERVER superglobal - SERVER_NAME and HTTP_POST.

The question initially was "arean't these the same thing?" Chris answers:

There were several informative replies within the first few minutes, but there's more to this question than most people realize. In fact, I'm reminded of a blog entry from Zeev last year, where he warns against $_SERVER['SERVER_NAME'].

Zeev suggests that SERVER_NAME is pulled from the Host header from the remote user. Chris reminds us, also, of some disagreements with this view Zeev presented, namely from Rasmus. Chris then gives an example script to illustrate hos things area really handled - the variables use the given values when they're present in the request, but they still do default back to the ServerName when absent (so only in certain circumstances).