Depending on the type of device a user
may use all or some of the services - obviously they are about
35 different services available on a PC screen, about 15 services
on a PDA and only 8 services on a WAP mobile phone. – but
whatever he uses the content is always the good one : his.
The way we have organized the connection between the 3 levels
is based on Internet standard, which means that
a user weights on the server only when he clicks a command. As
soon as the transaction is over, the server rests waiting for another
A classical transaction is a select or a insert instruction or a XML search
of a few characters – something like "select mobile phone number
where name is Jean Marc" which is a dummy operation for any database or
XML base that takes no time or computing resource.
Because most of end user's time is in reading or typing information, the server
can serve many clients registered at the same time without problem.
Another important asset, is that what we are working with personal
productivity and communication content. Most of it is not bandwidth
consuming – usually a user types about 30 words a minute
which is something like 0.5 kb, and requires hardly 5KB a minute
for its reading –
Therefore TAPP© encounters no problem when up scaling services to more users
or more content.