[Twisted-Python] loseConnection should stop the int32/int16 stringReceived too

[Andrea Arcangeli]

On Mon, Mar 14, 2005 at 12:58:47PM +0000, Jp Calderone wrote:
>   If the feature is desired somewhere else, the best way to add it is
>   to either find another way that doesn't rely on
>   transport.disconnecting (and then we can fix LineReceiver too), or
>   factor the code such that all protocols can provide the feature
>   without having more than one method that relies on
>   transport.disconnecting (then we can fix them all at once someday).

If there's no real generic API and you're not planning on adding it
soon, perhaps we could check it with hasattr and spawn a warning if the
transport doens't provide .disconnecting?