W3C home > Mailing lists > Public > www-mobile@w3.org > November 2001

RE: CC/PP profile repository overworked?

From: Olivier Rovellotti <olivier.rovellotti@3tl.com>
Date: Wed, 21 Nov 2001 10:08:44 -0000
To: "'Johan Hjelm'" <johan.hjelm@era-t.ericsson.se>, <nick.denny@mci.co.uk>
Cc: <www-mobile@w3.org>
Message-ID: <000201c17274$81a2fdc0$2f010a0a@marseille.ns1.tinet.ie>
The double click model is, as far as I know slightly different:
	1) There are an awfull lot more adds that their are devices
	2) There are a number of specialized servers in  the double-click network

Why not ask the manufacturer to maintain the profile repository for the
devices they are commercializing, that way we are putting the effort onto a
commercial organization which should have the financial power to make a good
job of it.

Just a suggestion
Olivier

-----Original Message-----
From: www-mobile-request@w3.org [mailto:www-mobile-request@w3.org]On
Behalf Of Johan Hjelm
Sent: Wednesday, November 21, 2001 5:15 AM
To: nick.denny@mci.co.uk
Cc: www-mobile@w3.org
Subject: Re: CC/PP profile repository overworked?


Mark is right, here are a couple of additional points:

If there was only one repository, that might be the case. However, since the
idea is that the repository will be distributed, residing in the profile
creators website, we see small risk of this. Other traffic (e.g. fetching
advertisements to web pages) already follow this model, and I have yet to
hear
that Doubleclick is to be overworked....

Secondly, the profile is cached in the proxy retrieving the information for
the client when it has been read once. So the traffic will not be as large
as
it sounds. The WAP gateway acts as a HTTP 1.1 proxy on the Internet side; at
least, this was how we intended it to be implemented. The profile-diff can
actually be a difference from an empty profile (of course you have to send
the
empty profile first), this is how it is used to combine P3P with CC/PP in
the
PIMI method.

Johan

nick.denny@mci.co.uk wrote:

> Hello,
>
> I'm in some confusion about CC/PP, specifically with regards to a CC/PP
> profile repository.
>
> Having read the CC/PP exchange protocol, section 6, the examples show
> that the profile information is sent as a list of URLs in the HTTP
> header. These URLs point to profile information of a CC/PP profile
> repository, which I understand can be any web server. So, if a user is
> viewing several web/wapsites, and every Origin server is CC/PP
> compliant, will this mean that the CC/PP profile repository will be
> accessed by every visited Origin server? Therefore, with potentially
> millions of people accessing different websites throughout the world,
> won't the CC/PP profile repository become highly over-worked, and if the
> CC/PP profile server, the Origin server and the end-user are all several
> routers apart, won't this add a large delay for the end-user?
>
> Thank you in advance,
>
> Nick Denny
> nick.denny@mci.co.uk
>
>   ------------------------------------------------------------------------
>                   Name: WINMAIL.DAT
>    WINMAIL.DAT    Type: application/ms-tnef
>               Encoding: base64

--
++++++++++++++++++++++++++++++++++++
  Johan Hjelm, Senior Specialist
     Ericsson Research Japan

  "Do you want to sell sugar water or
change the world" is the wrong question.
  The right question is: "How do you
change the world by selling sugar water?"

  Read more about my recent book
http://www.wireless-information.net
************************************
Received on Wednesday, 21 November 2001 05:00:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:16:03 UTC