Documentation of stream handling is unclear about actix HOT 9 CLOSED

I think add_feature is meant to be spawn. That said I cannot figure out what it is suppose to do.

from actix.

sorry, I am a bit busy at the moment. I will fix doc in few hours

from actix.

@fafhrd91 I can take on updating docs for StreamHandler since I was using it recently.
I think add_stream should refer to StreamHandler and there we can add all needed information on how it should work

from actix.

@DoumanAsh sure

from actix.

No worries.

In meantime is there a way of blocking stream I don't see? I can implement it myself but IMHO it looks kind of awkward.

from actix.

You can just create timeout future and wait for it. While waiting actor is paused

from actix.

@fafhrd91 I know but I don't want to pause actor - I want to pause the stream (or rather processing of stream). Given your comment I'm assuming there isn't such thing despite quoted comment suggesting otherwise.

This gets slightly off-topic but the comment suggested there was some way I could block stream. I'm assuming it happens with add_message_stream when I return a Future but it doesn't seem to do so (my underlying problem is that I want two websocket threads to communicate. However if I wait and they both try to send messages they will deadlock).

from actix.

@uzytkownik You can move to gitter chat for off-topic. But note that even if you want to block only stream, you're likely to block everything else by it too unless you convert it to ActorFuture

from actix.

updated

from actix.