On 7/25/07, Maarten Bosteels <[EMAIL PROTECTED]> wrote:
On 7/25/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
>
> Hi Luis,
>
> On 7/24/07, Luis Neves <[EMAIL PROTECTED]> wrote:
> > Yeah... my problem is with the "eventually" part, I really need a
> suspendReadNow().
>
> I see. Then why don't you create a JIRA issue? We could add
> TrafficControlFuture or something similar to trunk. Once implemented,
> you could do like the following:
>
> session.suspendRead().await();
Trustin,
Although a TrafficControlFuture might be useful, it won't help in this use
case: he wants to block the producer who
sits at the other side of the wire. I think best way to go is to do this at
the protocol level, as he mentioned.
You are right. I guess we can take care of this issue by calling
traffic control methods *before* ExecutorFilter in the filter chain.
It will fragment the protocol logic though.
SocketIoProcessor could check if the traffic mask has changed after
each read, and stop reading the current channel for precise traffic
control.
WDYT?
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
