The Case for Server Side Digital Information Applications with particular reference to ‘Voice Out’
Summary of the Server Side Case
4.0 Introduction
From the foregoing, it is clear that there is a strong case for server over client side services. This Chapter gathers together previous evidence into an easy reference summary:
4.1 Supplier Responsibility
When most people access information services what they want is a 'broadcast-like experience' (see 5.5) they do not want to be told that, in their absence from the keyboard, they have "performed an illegal operation" and they do not want to be harassed with error messages that imply they have made an error. This kind of technological confrontation is intimidating. People expect suppliers to take responsibility for errors or malfunctioning in products.
Clearly, an information system supplied from a 'remote' source to a thin client or fat phone with the supplier taking responsibility for the quality of service is an attractive proposition to people (not least women) who are not interested in the process of working with a digital information system but judge it on its output.
4.2. Branded Brokerage
A key development as the content on the World Wide Web continues to expand will be branded brokerage. Unlike a 'walled garden' this will simply be one option on a menu which will include access to all Web content but systems that monitor consumption and design offerings for end users will become ever more popular. It is possible to construct client side models for this kind of service but that is simply one more piece of redundant software and process. People are used to brand value analysis in retail and entertainment as well as broadcasting; there is a special case for child protection.
4.3 Child Protection
PIN-protected services with client side software are not very effective at protecting children from material likely to cause harm or offence. It might be argued that parents and carers give way too easily to children but there is still a strong case for supply side measures to assist them, particularly in the context of an internet where content is unregulated by national authorities or ISPs. A supply side service could limit certain user interfaces to certain branded material; and it could alert 'related' devices to attempts to access un permitted material.
It is, however, important to remember that there is a server disjuncture between what people say they want and what they do; there is massive 'political' pressure for child protection but a much lower level of parent/carer action even where it is possible. This is a complex area of public policy.
4.4 Centralised Services
It is clear beyond doubt that centralised services such as:
- Error correction
- Upgrading
- Junk Mail Filtering and
- Virus protection
- Error Correction. are much more effectively carried out at the level of a centralised server. Instead of hundreds of technicians working all over the planet on individual client side packages, one technician can correct the central fault for all subscribers.
- Upgrading. In a server side situation upgrading clearly becomes the responsibility of the supplier who operates on supplier equipment; there is no customer invasion or interference with settings. Any upgrading will be guaranteed to be trouble free for accredited hardware devices. Again, the multiple technician element will be eliminated.
- Junk Mail Filtering. The advantages of centralised junk mail filtering are that:
- End users can choose from various levels of shielding from none at all to 'high consensus'
- Database analysis of incoming mail and user reaction (deletion without opening) can establish various 'consensus' levels for filtering
- Users can specify domains for automatic exclusion (eg: .ng for Nigeria or even .com)
- Virus Protection. The imposition of consumer responsibility for virus protection is perverse, risky and inefficient. As with general filtering, users of a server side service can choose to take personal responsibility or opt for centralised protection.
4.5. Centralised Accessibility
This subject will be dealt with in detail in Chapter 5 but what applies to 4.3 and 4.4 also applies here.
4.6 Lower Unit Cost
Accessing branded server side information services through thin clients or fat phones is cheaper in terms of hardware, software, maintenance cost and time than using PC/Apple client side hardware and software to access the undifferentiated internet.
4.7 Cost Stability
It is impossible to calculate accurately the cost of purchasing and maintaining a PC/Apple client side package because of uncertainties over:
- Support
- Upgrading
- Backwards compatibility
- Lack of consumer rights
- Virus invasion.
Subscription server side supply models mitigate all of these uncertain factors.
4.8 The Green Dividend
Client side services have a much larger 'carbon footprint' than server side applications as follows:
- More hardware
- More software
- More maintenance miles
- More power consumption
- More wasted search time.
4.9 Generic User Requirement
The EU regulatory framework which has been relatively hostile to proprietary client side suppliers would be equally hostile to public sector interference in the market to establish server side services; the only viable route to achieving the objectives in this Chapter is the use of generic user requirements as the driver behind procurement.