Re: [hybi] Multiplexing: Pre-AddChannelResponse quota

[Takeshi Yoshino <[e-mail]>]

On Fri, Jun 15, 2012 at 5:21 PM, Arman Djusupov <[e-mail]> wrote:

> Since we go that far in flexibility why not just give the client a quota
> and let it distribute it in the channels any way the client likes. This way
> the client will be able to give a higher or lower priority to newly
> established channels. The client will need to state the amount of quota it
> assigned to a channel slot when sending an AddChannelRequest. So when
> receiving a PreHandshakeQuota the client does not level it between
> available slots, but uses a share of this quota later when creating a new
> channel. This would be a simplified common quota.
>

I still wonder if grabbing per-channel basis quota control away from
server-side (which post-handshake quota allows for) makes sense or not.
Pre-handshake data processing may be designed similarly as post-handshake.

Algorithm based on your proposal would be like this:

- NC_WIN = 0
-- # of future/in-flight AddChannelRequest <= NC_WIN
-- When received, say, NewChannelQuota block, add the value to NC_WIN
- PQ = 0
-- When received, say, PreHandshakeQuota block, add the value to PQ
- To issue an AddChannelRequest with channel ID X
-- On AddChannelRequest, the client declares the amount of PQ to assign for
X (IQ_X)
-- PQ = PQ - IQ_X
-- The quota for channel X is initialized to be IQ_X (can be used for both
pre- and post-handshake data)
- When received the corresponding AddChannelResponse, NC_WIN = NC_WIN - 1

Very simple. Assignment to channels is done by client-side (different from
post-handshake). Am I understanding correctly?