- Updating Device Data
- Web Apps
- Reference Pages
- Useful Links
- Supported Versions
This tutorial illustrates how to use the findProfiles function to return a list of matching profiles for a given property value pair. The following steps are covered:
- How to find all the mobile device profiles.
- Find all the mobile profiles with a screen size of 1080 pixels.
- Do the same for non-mobile devices, and display how many have that screen size.
Code and Explanation
Specify name of the data file and properties the dataset should be
const char* fileName = argv; const char* properties = "IsMobile";
Instantiate the 51Degrees provider from the specified data file with
the required properties, number of worksets in the pool and cache of the
fiftyoneDegreesInitProviderWithPropertyString( fileName, &provider, properties, 4, 1000);
Retrieve all the profiles from the data set which match a specified
property value pair.
fiftyoneDegreesProfilesStruct *profiles = provider.findProfiles("IsMobile", "True");
Free the memory taken by the profiles structure
Finally release the memory taken by the provider
This example assumes you have compiled with 51Degrees.c and city.c. This will happen automatically if you are compiling as part of the Visual Studio solution. Additionally, when running the program, the location of a 51Degrees data file must be passed as a command line argument if you wish to use Premium or Enterprise data files.
The size of the worksets pool parameter should be set to the maximum (expected) number of concurrent detections to avoid delays related to waiting for free worksets. Workset pool is thread safe. Initially the number of created worksets in the pool is zero. When a workset is retrieved from the pool a new workset is created if no worksets are currently free and the number of worksets already created is less than the maximum size of the workset pool.
This tutorial covered how to work with the 51Degrees device Data Model to obtain a subset of device profiles that meet several conditions. Each condition in this case is a specific value for a chosen property. The result should be read as follows: this is a subset of device profiles where property1 has value1 and property2 has value2 and property3 has value3 and so on.
One real world application for this is building a set of interlinked menus where each choice will narrow down the available options for subsequent choices. This can be useful when part of the API is exposed to the end user:
- An ad agency could benefit from allowing their clients to target specific devices based on pre-defined criteria, such as DeviceType, ScreenInchesWidth or even PriceBand.
- A program that uses a 51Degrees API to generate/augment reports could be enhanced to allow the user to choose the report parameters. By p roviding a finite set of choices and avoiding arbitrary input the chance of errors occurring is reduced and user experience improved.
The Lite data file contains considerably fewer properties and values than the Premium or Enterprise files, making the usefulness of this tutorial slightly harder to appreciate. With Premium and Enterprise data files there are many more possibilities for creating subsets of device profiles. For example: using Premium device data you can generate a subset of all ' Samsung ' ' Smartphone ' devices. Or get all the properties of a specific HTC model.