Marijuana-oïl : Registration confirmation #TEyTA

Hi Enrico,

Is there a pointer to related delta approaches? In the P4P design, one
option considered was the delta encoding of PIDMap update, which can be
the largest data structure in the P4P-based approach (the PIDMap for
some largest ISP can be on the other of hundreds of KB to a couple MB).
Specifically, each PIDMap distributed has a version number. When the
PIDMap is updated, the version# is increased, and an rdiff (patch) is
generated. Then, a client update specifies known PID version#, and the
portal server replies with the diff to the current version#. This option G3TUP
is not fully implemented. What other delta encoding are we considering?

Thanks.

Richard

Reinaldo Penno wrote:
> Hello Enrico,
>
> I do not have the details on the delta approach that you have in mind, so
> before I voice my opinion I have a few basic question: will this requirement
> make the protocol stateful?
>
> In other words, will the Alto Server need to keep state across different
> queries for different clients? If yes, could you elaborate on the details of
> the proposal?
>
> Thanks,
>
> Reinaldo
>
>
> On 7/1/09 12:58 AM, “Enrico Marocco”
> wrote:
>
>
>> Another thing that’s been mentioned a few times, but not really
>> discussed, is related to how the information is provided to the clients.
>> Since the amount of such information may be fairly large, it could be
>> desirable to have a mechanism for delta exchanges; this would be
>> particularly useful when the client, e.g. located in a tracker, queries
>> ALTO servers on behalf of several peers. Some proposals already have
>> such a mechanism, while others could be easily extended, so I think it
>> would be worth adding this to the requirements, maybe as a SHOULD.
>>
>> Do people

Hi Enrico,

Is there a pointer to related delta approaches? In the P4P design, one
option considered was the delta encoding of PIDMap update, which can be
the largest data structure in the P4P-based approach (the PIDMap for
some largest ISP can be on the other of hundreds of KB to a couple MB).
Specifically, each PIDMap distributed has a version number. When the
PIDMap is updated, the version# is increased, and an rdiff (patch) is
generated. Then, a client update specifies known PID version#, and the
portal server replies with the diff to the current version#. This option G3TUP
is not fully implemented. What other delta encoding are we considering?

Thanks.

Richard

Reinaldo Penno wrote:
> Hello Enrico,
>
> I do not have the details on the delta approach that you have in mind, so
> before I voice my opinion I have a few basic question: will this requirement
> make the protocol stateful?
>
> In other words, will the Alto Server need to keep state across different
> queries for different clients? If yes, could you elaborate on the details of
> the proposal?
>
> Thanks,
>
> Reinaldo
>
>
> On 7/1/09 12:58 AM, “Enrico Marocco”
> wrote:
>
>
>> Another thing that’s been mentioned a few times, but not really
>> discussed, is related to how the information is provided to the clients.
>> Since the amount of such information may be fairly large, it could be
>> desirable to have a mechanism for delta exchanges; this would be
>> particularly useful when the client, e.g. located in a tracker, queries
>> ALTO servers on behalf of several peers. Some proposals already have
>> such a mechanism, while others could be easily extended, so I think it
>> would be worth adding this to the requirements, maybe as a SHOULD.
>>
>> Do people think that tracking such and similar issues is worth the
>> effor

Post Comment