您现在的位置: IOS教程網 >> IOS系統 >  >> iOS 使用技巧 >> iOS 技巧大全

ReactiveCocoa 中的 replay、replayLast 與 replayLazily 差在哪

編輯:iOS 技巧大全

replayLazily 為什麼能直接跳到最後一格?這個問題我卡了很久。原文:https://spin.atomicobject.com/2014/06/29/replay-replaylast-replaylazily/

最近同事問起這三個方法的差異,我發現自己也說不清楚,於是乾脆做了一輪深入研究。如果對 RACReplaySubject 與 RACMulticastConnection 沒有概念,直接讀 header 裡的說明會非常吃力,所以下面先從行為觀察切入。

先理解普通 signal 的訂閱

對一個「普通」的 signal 來說,每次訂閱都會讓 signal 內部的程式碼重新執行一次,而該次訂閱者只會收到這一次產生的值。

__block int num = 0;
RACSignal *signal = [RACSignal createSignal:^RACDisposable *(id subscriber) {
    num++;
    NSLog(@"Increment num to: %i", num);
    [subscriber sendNext:@(num)];
    return nil;
}];

NSLog(@"Start subscriptions");

[signal subscribeNext:^(id x) { NSLog(@"S1: %@", x); }];   // Subscriber 1
[signal subscribeNext:^(id x) { NSLog(@"S2: %@", x); }];   // Subscriber 2
[signal subscribeNext:^(id x) { NSLog(@"S3: %@", x); }];   // Subscriber 3

執行結果:

Start subscriptions
Increment num to: 1
S1: 1
Increment num to: 2
S2: 2
Increment num to: 3
S3: 3

num 每次訂閱都遞增,若完全沒有訂閱者則根本不會遞增。這說明了 signal 是「懶」的:沒有訂閱就不執行。

再看訂閱時機如何影響值的接收:

RACSubject *letters = [RACSubject subject];
RACSignal *signal = letters;

NSLog(@"Subscribe S1");
[signal subscribeNext:^(id x) { NSLog(@"S1: %@", x); }];

NSLog(@"Send A");  [letters sendNext:@"A"];
NSLog(@"Send B");  [letters sendNext:@"B"];

NSLog(@"Subscribe S2");
[signal subscribeNext:^(id x) { NSLog(@"S2: %@", x); }];

NSLog(@"Send C");  [letters sendNext:@"C"];
NSLog(@"Send D");  [letters sendNext:@"D"];

NSLog(@"Subscribe S3");
[signal subscribeNext:^(id x) { NSLog(@"S3: %@", x); }];

執行結果:

Subscribe S1
Send A
S1: A
Send B
S1: B
Subscribe S2
Send C
S1: C
S2: C
Send D
S1: D
S2: D
Subscribe S3

S2 只收到訂閱之後才送出的 C、D;S3 什麼都沒收到。多數情況這正是我們想要的,但有兩類需求它滿足不了:一是希望不管多少個監聽者,網路請求只送出一趟;二是希望後加入的訂閱者能拿到訂閱之前已經送過的值。-replay、-replayLast 與 -replayLazily 就是為了解決這兩件事而生。

-replay

它會回傳一個新的 signal。當源 signal 被訂閱時,訂閱者會立刻收到全部歷史值,而且不會重複執行源 signal 的訂閱程式碼;之後新送出的值同樣會收到。

__block int num = 0;
RACSignal *signal = [[RACSignal createSignal:^RACDisposable *(id subscriber) {
    num++;
    NSLog(@"Increment num to: %i", num);
    [subscriber sendNext:@(num)];
    return nil;
}] replay];

NSLog(@"Start subscriptions");

[signal subscribeNext:^(id x) { NSLog(@"S1: %@", x); }];
[signal subscribeNext:^(id x) { NSLog(@"S2: %@", x); }];
[signal subscribeNext:^(id x) { NSLog(@"S3: %@", x); }];
Increment num to: 1
Start subscriptions
S1: 1
S2: 1
S3: 1

num 在首次訂閱時就遞增,而且只遞增一次。不管有多少訂閱者,裡面的程式碼只跑一輪。

RACSubject *letters = [RACSubject subject];
RACSignal *signal = [letters replay];

NSLog(@"Subscribe S1");
[signal subscribeNext:^(id x) { NSLog(@"S1: %@", x); }];

NSLog(@"Send A");  [letters sendNext:@"A"];
NSLog(@"Send B");  [letters sendNext:@"B"];

NSLog(@"Subscribe S2");
[signal subscribeNext:^(id x) { NSLog(@"S2: %@", x); }];

NSLog(@"Send C");  [letters sendNext:@"C"];
NSLog(@"Send D");  [letters sendNext:@"D"];

NSLog(@"Subscribe S3");
[signal subscribeNext:^(id x) { NSLog(@"S3: %@", x); }];
Subscribe S1
Send A
S1: A
Send B
S1: B
Subscribe S2
S2: A
S2: B
Send C
S1: C
S2: C
Send D
S1: D
S2: D
Subscribe S3
S3: A
S3: B
S3: C
S3: D

即使 S3 是在所有值都送完之後才訂閱,仍然完整收到了 A、B、C、D。

-replayLast

行為與 replay 幾乎一致,唯一差別是訂閱時只補送「最新的一個值」,而非全部歷史。它同樣不會重複執行源 signal 的程式碼,之後的新值也會照常收到。

RACSubject *letters = [RACSubject subject];
RACSignal *signal = [letters replayLast];

NSLog(@"Subscribe S1");
[signal subscribeNext:^(id x) { NSLog(@"S1: %@", x); }];

NSLog(@"Send A");  [letters sendNext:@"A"];
NSLog(@"Send B");  [letters sendNext:@"B"];

NSLog(@"Subscribe S2");
[signal subscribeNext:^(id x) { NSLog(@"S2: %@", x); }];

NSLog(@"Send C");  [letters sendNext:@"C"];
NSLog(@"Send D");  [letters sendNext:@"D"];

NSLog(@"Subscribe S3");
[signal subscribeNext:^(id x) { NSLog(@"S3: %@", x); }];
Subscribe S1
Send A
S1: A
Send B
S1: B
Subscribe S2
S2: B
Send C
S1: C
S2: C
Send D
S1: D
S2: D
Subscribe S3
S3: D

S2 只拿到 B,S3 只拿到 D。這個特性很適合「目前狀態」這類語義——例如當前登入使用者、最新一筆價格,新訂閱者只需要知道現在是什麼,不必重放整段歷史。

-replayLazily

它同樣會把全部歷史值補送給新訂閱者,也不重複執行源程式碼。與 replay 的關鍵差異在於時機:replayLazily 在有人真正訂閱之前,完全不會去訂閱源 signal。也就是說,直到第一次訂閱發生,signal 才被真正建立起來,裡面的程式碼才開始跑。

__block int num = 0;
RACSignal *signal = [[RACSignal createSignal:^RACDisposable *(id subscriber) {
    num++;
    NSLog(@"Increment num to: %i", num);
    [subscriber sendNext:@(num)];
    return nil;
}] replayLazily];

NSLog(@"Start subscriptions");

[signal subscribeNext:^(id x) { NSLog(@"S1: %@", x); }];
[signal subscribeNext:^(id x) { NSLog(@"S2: %@", x); }];
[signal subscribeNext:^(id x) { NSLog(@"S3: %@", x); }];
Start subscriptions
Increment num to: 1
S1: 1
S2: 1
S3: 1

把這段輸出跟 replay 的版本對照,順序差異一目了然:replay 在呼叫 replay 的那一刻就訂閱了源 signal,「Increment num to: 1」印在 Start subscriptions 之前;replayLazily 則要等到實際訂閱才印。這個差異看似細微,實務上卻很關鍵——如果 signal 背後包著昂貴的資源(網路連線、檔案、感測器),用 replayLazily 可以避免它在無人使用時就被白白啟動。

RACSubject *letters = [RACSubject subject];
RACSignal *signal = [letters replayLazily];

NSLog(@"Subscribe S1");
[signal subscribeNext:^(id x) { NSLog(@"S1: %@", x); }];

NSLog(@"Send A");  [letters sendNext:@"A"];
NSLog(@"Send B");  [letters sendNext:@"B"];

NSLog(@"Subscribe S2");
[signal subscribeNext:^(id x) { NSLog(@"S2: %@", x); }];

NSLog(@"Send C");  [letters sendNext:@"C"];
NSLog(@"Send D");  [letters sendNext:@"D"];

NSLog(@"Subscribe S3");
[signal subscribeNext:^(id x) { NSLog(@"S3: %@", x); }];
Subscribe S1
Send A
S1: A
Send B
S1: B
Subscribe S2
S2: A
S2: B
Send C
S1: C
S2: C
Send D
S1: D
S2: D
Subscribe S3
S3: A
S3: B
S3: C
S3: D

就「補送哪些值」而言,它的行為與 replay 完全相同。

總結

ReactiveCocoa 用這三個方法解決了同一類問題:讓多個訂閱者共享一個 signal,不重複執行訂閱程式碼,並能為新加入者補送訂閱前的值。差別在於兩點——補送範圍(全部或最新一個)與啟動時機(立即或延後)。replay 與 replayLast 會立刻把 signal 變成熱 signal,分別補送全部值與最新值;replayLazily 則回傳冷 signal,等到首次訂閱才啟動,並補送全部值。

  1. 上一篇文章:
  2. 下一篇文章:
蘋果刷機越獄教程| IOS教程問題解答| IOS技巧綜合| IOS7技巧| IOS8教程
Copyright © IOS教程網 All Rights Reserved