The client can type in a score filter and choose to apply
this filter by selecting the corresponding checkbox. The
score filter will automatically eliminate all the components
that have a lower score than the filter, and store all the
components with a higher score into the database. The
mobilizer also offers a preview functionality to let the clients
access the appearance of the web page after they make their
choice on components.
The content retrieving logic is as follows. First, the web
page mobilizer will try to detect whether there is a stored
mapping in the database. If not, it will convert the entire
page content through the mobilization process described
earlier. If there exist rules that have been selected by the
client, it will first load the IDs from the rule applied for the
whole domain, and then load the IDs specified for this page.
Then, it will compare all the loaded IDs to the exclusions
list. If the ID has been listed as excluded by the client, then
the mobilizer will delete the ID from the loading list. At the
completion of this process, the mobilizer will have obtained
which components should be kept, and then extract all the
HTML content from the existing web page. The final HTML
content is now ready to be sent back to the customer’s
mobile device.