Skip navigation

Category Archives: Developement

This is a bit of a rant, those of the public that dislike reading ranting and raving blog post turn away now.

I’ve become quiet sick of hearing about how certain techniques or ways to build or have to do with web sites in general is either good or bad for search engines. The last time I checked a web site is not made for search engines, a web site if for the human users that access it. Majority of amateur developers (if you can call them that) use a false idea of “SEO” to base their decisions on. Seems to be a lack of web developers out there focus on the actual users and their needs!

It is really very simple to make a web sites work for both human users and search engine robots. Make use of web standards, semantic HTML, good, useful, and unique content that is updated all the time. You do not even need to worry about if your site is using CSS or Javascript, when done right they will have no effect on the users or search engines. Of course being used right means, the site does not depend on CSS or Javascript to function.

Choosing a technology or technique for a web site should not be based on “SEO” but rather the human users that are going to be using the site.

</rant>

Previous Post is here.

Made quite a few changes to the interface since the last time I posted. It was becoming far too complex for something that needed to be so simple. The end result has the removal of the independent parser class and segment classes.

The parsing is all handled though the single class along with the segments. However, complex types like the path and query string segments are set into there own classes to be referenced from there.

That is all I have to report right now, steadily working on simplifying the interfaces for this project as I write it up. Oh right another thing, I’m avoid a lot of the built in PHP functions like parse_url, parse_str, and http_build_query because I wouldn’t learn anything that way.

In the previous post the example given is now invalid. How it should be:

   1:  // __load.php contains the autoloading which is required!
   2:  // Without it this library will not function correctly.
   3:  require_once '/path/lfUri/library/__load.php';
   4:  
   5:  $url = 'http://example.com:8080/path/to/no/where.ext';
   6:  $url = new lfUriLocator( $url );
   7:  
   8:  var_dump( $url->getScheme() );
   9:  var_dump( $url->setScheme( 'ftp' )->getScheme() );
  10:  
  11:  // Only for the development stages will the parser object contain
  12:  // a means to construct a URL from parts. Debugging use only.
  13:  print $url; # $url->__toString();

The project source files can be found at Google Code
http://code.google.com/p/lfuri/