Am 02.03.2015 um 17:09 schrieb Ivan Komarov:
> What I have in mind, is a situation when frequent lighweight requests
> are mixed with rare heavy ones and I don't want to see the latter ones
> completely blocking processing the formers.
Ah, so you a concerned about so called "head of line blocking" at the
(single) transport level.
A single, standard WebSocket transport can't interleave messages. Once
message has started to be sent out / or received, everything for that
message needs to go over the transport first.
This isn't specific to WAMP, but standard WebSocket.
Extensions to WebSocket could. See my proposal addressing exactly this
use case
https://github.com/oberstet/permessage-priority/blob/master/draft-oberstein-hybi-permessage-priority.txt
Note that WebSocket MUX and HTTP/2 have multiplexing of multiple
_connections_ over a single physical connection (TCP), but they don't
directly address interleaving _messages_ (allowing for priorization and
avoiding head-of-line blocking on a single channel).
/Tobias
> <mailto:
tobias.o...@gmail.com>> wrote:
>
> Am 02.03.2015 um 16:53 schrieb Ivan Komarov:
>
> Thanks Tobias,
>
> but while one (big) request is being sent from a Router to a
> Callee over
> the transport layer, other requests to the same Callee will be
> waiting
> for it to finish sending the data, right?
>
>
> Yes. On a given transport, there can be only 1 message currently
> being sent or received (WAMP messages cannot be fragmented and
> interleaved).
>
> If your transport is network bound (link bandwidth not enough), it
> does not matter how many TCPs you have open: they all will stall.
>
> You need to have callees on different machines, over different
> network links.
>
> This is possible with Crossbar.io and the new "Shared Registrations"
> feature.
>
> Cheers,
> /Tobias
>
> --
> You received this message because you are subscribed to a topic in
> the Google Groups "Autobahn" group.
> To unsubscribe from this topic, visit
>
https://groups.google.com/d/__topic/autobahnws/25vCssyMe14/__unsubscribe
> <
https://groups.google.com/d/topic/autobahnws/25vCssyMe14/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to
> autobahnws+unsubscribe@__
googlegroups.com
> <mailto:
autobahnws%2Bunsu...@googlegroups.com>.
> <mailto:
autob...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/__msgid/autobahnws/54F4888B.__1030504%40gmail.com
> <
https://groups.google.com/d/msgid/autobahnws/54F4888B.1030504%40gmail.com>.
> For more options, visit
https://groups.google.com/d/__optout
> <
https://groups.google.com/d/optout>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Autobahn" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
autobahnws+...@googlegroups.com
> <mailto:
autobahnws+...@googlegroups.com>.
> <mailto:
autob...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/autobahnws/CAJDzOcZiaX1cKcWxnRjzo_bGeYgnyOH0H%2BQBV1U2hMQ7E0a1zA%40mail.gmail.com
> <
https://groups.google.com/d/msgid/autobahnws/CAJDzOcZiaX1cKcWxnRjzo_bGeYgnyOH0H%2BQBV1U2hMQ7E0a1zA%40mail.gmail.com?utm_medium=email&utm_source=footer>.