This takes an array of HTTP Headers, such as those in $_SERVER, which can be passed straight in, or you could use the getRandomTestHeader method to get a set from our database of 70,000 sample header strings from real devices. The array you get back consists of an associative array of keys and values representing the properties of the device and the customer. This array will vary in size depending on how much information is available, or how much can be derived in real-time by the system. There are also currently numerous performance-testing and diagnostic fields which should give you an idea of the amount of seconds the server spent on each profile. Normally you'd disregard those. You can also retrieve a previous customer you've seen from the database by passing their customer number (OK, it's an MD5) into the getCustomer function. This allows you to keep your own local database of customer MD5s, or store the MD5 in a cookie as an alternative to using a PHP session ID Since this customer number can be stored and used to store cookies (and even objects) against a customer (independently of whether their actual device supports them), the customer number is handy. You could also use it for retrieving for the purposes of reporting later. The comment field is to allow you to associate the page view with a real-world comment. This will be handy later when our reporting interface is available, since you'll be able to track customers' page views: the comments will allow you to insert sensible comments or events, such as "looked at Axel F", "about to buy xxxxxx", "successfully paid for xxxx", etc. For this to work, the "SCRIPT_URI" header has to be present to indicate which page is calling DetectRight. You can call getCustomer multiple times on the same page if you want to insert multiple comments. The "test" option allows you to have returned a profile based on one of our test headers. Gets a sorted list of manufacturers we have seen phones for in the massive DetectRight data warehouse. Very useful for constructing option lists to allow customers to choose the manufacturer of their phone. Plans are afoot to even further standardise the list to compensate for manufacturers not being entirely sure what their name is. Gets a device profile for a given manufacturer and model number (e.g. "Nokia","3510"). The DetectRight system contains multiple profiles for any given combination of model name and manufacturer. The system picks the latest seen profile for a given manufacturer/model, since this is least likely to be an experimental profile (DetectRight sees many preview phones which have incorrect or incomplete headers or UAProfs). Schemaname is for full DetectRight Clients, who can save on data throughput by specifying a named set of profile fields of interest to filter the profile by. For instance, a DetectRight Client could create a "Java" profile which only includes chosen Java-related fields. If this field is left blank, then you get all fields. This would be a good time to note that there are few profile fields in an DetectRight profile that are guaranteed to be in the profile on all occasions. The fact that a profile field is missing from a returned profile is a valid item of information: that we don't know what that data is. We are philosphically against returning false generic data to pad out a schema. We go to every length to extract all the information we possibly can for a device, though. Gets a device profile from a given User Agent. Use of the accept string in this function has been obviated. Gets a device profile from a given User Agent: includes adaptive processing. This function is deprecated. Gets a device profile from an associative array containing values for the keys HTTP_USER_AGENT. Gets a sorted list of models given a manufacturer. This function raids our database for one of our test phone http header arrays. We've got about 70,000, which are useful for testing the variety of devices out there. If you're testing this client software, then you might want to get an associative array to pass to getCustomer from this function. Returns an array of cookies which are also put into the DetectRight object. Unlike in the PHP Client code, cookie values here can only be strings. Obviously that can be serialized can be used as a cookie by you, with the proviso that the total size of a gzipped, base64 encoded cookie can't be greater than 16K. This size limit is subject to review, of course. Note that despite the name, these cookies are not stored in the browser, though there's nothing stopping you extending this code to do just that. To use getcookies sensibly, you must have seen the customer. You will not be allowed to retrieve the cookies against customers that aren't tied to your licence number. Sets the cookies for a customer. This has two steps: synchronise the local cookie collection and transmit the new cookies to the database. When the cookies get to the DetectRight Service, they're merged with the current cookies. You can't delete cookies by setting them to empty. Deletes a particular cookie, both locally and from the DetectRight Service. Deletes all cookies for a customer.