16

Using ReactiveCocoa, there seem to be two ways to have subscribers receive the same values from a signal, rather than re-triggering whatever operation generates those values: Via RACReplaySubject or RACMulticastConnection.

Here are the header docs for RACReplaySubject:

A replay subject saves the values it is sent (up to its defined capacity) and resends those to new subscribers. It will also replay an error or completion.

And for RACMulticastConnection:

A multicast connection encapsulates the idea of sharing one subscription to a signal to many subscribers. This is most often needed if the subscription to the underlying signal involves side-effects or shouldn't be called more than once.

The multicasted signal is only subscribed to when -[RACMulticastConnection connect] is called. Until that happens, no values will be sent on signal. See -[RACMulticastConnection autoconnect] for how -[RACMulticastConnection connect] can be called automatically.

Note that you shouldn't create RACMulticastConnection manually. Instead use -[RACSignal publish] or -[RACSignal multicast:].

Can someone provide simple guidelines as to when you would use RACReplaySubject or RACMulticastConnection?

Roman B.
  • 3,598
  • 1
  • 25
  • 21
Poulsbo
  • 648
  • 5
  • 18

1 Answers1

33

Actually, they're not mutually exclusive, and can even be used together.

The main purpose of RACMulticastConnection is to subscribe to a base signal, and then multicast that subscription to any number of other subscribers, without triggering the base signal's side effects multiple times.

RACMulticastConnection accomplishes this by sending values to a private RACSubject, which is exposed via the connection's signal property. Subscribers attach to the subject (which doesn't cause any side effects), and the connection forwards all of the base signal's events there.

There are a few different methods to create a connection:

  • The -publish creates a connection with a plain RACSubject. This subject will not replay previous values to new subscribers.
  • The -multicast: method creates a connection with a subject of your choice. You could decide to use a RACReplaySubject here.
  • The -replay, -replayLast, and -replayLazily methods are conveniences for creating a connection with a RACReplaySubject, and then also automatically connecting to it.

If in doubt, -replayLazily will probably do what you want, because it saves all values and only triggers any side effects (or starts any work) when the returned signal receives a subscription.

Justin Spahr-Summers
  • 16,893
  • 2
  • 61
  • 79
  • Would RACMulticastConnection be appropriate for the "onMessage" block of a WebSocket Client? Then, the subscribers can filter appropriately what do do with different data types? – Max Alexander Nov 09 '14 at 10:45
  • @MaxAlexander You may want to open a separate question for that, as I don't think I can answer it without more details. – Justin Spahr-Summers Nov 10 '14 at 18:39
  • @JustinSpahr-Summers what would you recommend to use with AFNetworking rac_GET, rac_POST... signals inside of RACCommand? `replayLazily` or `replayLast`? – Nik May 02 '15 at 21:32
  • @JustinSpahr-Summers. Is there anyway we can model a one and only subscriber at once. I simply want to model this http://stackoverflow.com/questions/36026927/reactive-cocoa-limit-a-signal-to-only-one-subscriber-at-once – Swift Hipster Jun 07 '16 at 10:36