What increased bandwidth for the merchant might be required to handle transactions? What share of total costs would arise from communications (bandwidth) both for the publishers and Clickshare?
Sadly, we are not able to provide anything but a heuristic answer to this at this time: Our service is as low bandwidth as is possible with today’s IP technology. In the model where service providers and publishers are distinct, publishers will see very limited bandwidth decay due to our service alone. The service providers, who are likely to be providing a set of auxiliary Clickshare services to users (daily expense reports, balances, transaction history, etc) will see more decay certainly. But, overall there are fewer than 1000 bytes per request – actually fewer than 500. So, if one can (dare!) assume that the average URL request results in 8192 bytes sent to the client (which itself generates a lot of connection setup/tear down bandwidth), then our service adds 6% (including both authentication and logging in this value). Actually, we think bandwidth is not the concern. We think LATENCY is the concern. We have designed a system that is low-latency so that the consumer sees no “inter
