XML – Looks like this:
<user>
<name>tom</name>
<last_name>jackson</last_name>
<email>t.jackson@jackson.com</email>
</user>

vs.

JSON – Looks like this:
user{name:tom,last_name:jackson,email:t.jackson@jackson.com}

JSON reminds me of how a lighttpd configuration file is able to hold script in it. Meaning the file that hold information, holds simple code so you have less info to process. JSON can send arrays. So instead of XML parser reading through a node value and creating an array, JSON just sends the array! Instead of an XML parser that creates objects and its properties, JSON just sends the object with it’s properties.

So in the end, JSON just sends you the data you would just end up making with an XML file. Currently ActionScript 3.0 is going to support JSON, and so does JavaScript, but unless you are managing and sending large amounts of data, XML is good for communication… very good!

One of the best uses of Blackberrys:
http://www.impatica.com/imp4bes/

Over the past couple of years HTML has been merging with XML to make more of a sustainable standard for basic-web-coding. In the future when XHTML is more XML than original HTML, it will allow for more scripting prowess. Right now, XHTML is still a bit sketchy and a lot of companies keep exploiting the declartion of coding as ‘loose’. Which roughly translate to, “I can write a bunch of crappy code, that has tags and faulty attributes everywhere, and it’s not going to be a problem when a browser loads it, because they’re good at interpting garbage.”

That declaration of loose is going to change soon. And is alreading something that has to be incorporated into existing sites. I’m not saying that every web-page is going to stop working, but I am saying that those pages won’t be appearing to well on non-desktop devices and future browsers.
Currently their is ‘loose’, ‘transitional’ and ‘strict’ settings for XHTML 1.0. Loose, means “Code like crap… it’s fine.”. Transitional, means “I know you know HTML 4.0, and your getting the jist of it, but how about incorporating some XML into that page?”. And finally strict, means “You’re ready for XHTML 1.1. Good for you Billy!”.

Internet Explorer, the most common browser on the web, is always going to be holier than the pope, but it will be easier to code for once XHTML 1.1 is a widely-used standard.

The reason for making all HTML code XML, is to keep all elements and functionality of the site seperate. There are two other main elements going to be involved with pages, that are already prevelant. CSS and JavaScript. XHTML is going to use, and reliy on CSS for structuring and layout design, while JavaScript is going to be used for functionality in the DOM (Document Object Model). This will make it easier for a mulititude of devices to read the same page. Because those three elements will be split-up and not be interpretated the same, allowing the devices to decide how to interpreate the page, with-out screwing-up the over-all page.

DNSstuff.com is the best collected set of Domain Name information tools. They’re all free too.

Also they released a latency test tool, that’s free for download, titled LateRoute.

Magpie RSS is a PHP RSS parser that is extremely simple to install and use. Very flexible and highly optimized. Very well collected & written code.

When I write “PHP *something* parser”, it essentially means that the programming language PHP is analyizing and breaking down a data-file into components.
So a file that looks like this:

Green
Giant

Could be ‘parsed’ into: Green Giant

Definition of RSS