RAC的冷信号和热信号-RACSubject

RAC的冷信号和热信号

本篇目录

何为冷信号，热信号；
为何会有RACSubject这个类的存在；
RACSubject已经其子类的介绍；
如何将一个冷信号转成热信号。

何为冷信号，热信号？

冷信号：

RAC中的RACSiganl类中几乎都是冷信号,以+ (RACSignal *)createSignal:(RACDisposable * (^)(id<RACSubscriber> subscriber))didSubscribe方法为例：

+ (RACSignal *)createSignal:(RACDisposable * (^)(id<RACSubscriber> subscriber))didSubscribe {
    return [RACDynamicSignal createSignal:didSubscribe];
}

初始化一个RACDynamicSignal保存一个block，等到有订阅者去订阅，如果没有订阅者的话，一直不会被调用，也就是冷信号被调用的前提是要有订阅者，这就是冷信号；

热信号：

解释完冷信号，那热信号肯定是即使没有订阅者也是会发送消息的，是的rac提供了RACSubject，专门处理热信号的。

为何会有`RACSubject`这个类的存在？

要想解释为什么会存在RACSubject这个类，首先来一个场景

 self.sessionManager = [[AFHTTPSessionManager alloc] initWithBaseURL:[NSURL URLWithString:@"http://api.xxxx.com"]];

    self.sessionManager.requestSerializer = [AFJSONRequestSerializer serializer];
    self.sessionManager.responseSerializer = [AFJSONResponseSerializer serializer];

    @weakify(self)
    RACSignal *fetchData = [RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        @strongify(self)
        NSURLSessionDataTask *task = [self.sessionManager GET:@"fetchData" parameters:@{@"someParameter": @"someValue"} success:^(NSURLSessionDataTask *task, id responseObject) {
            [subscriber sendNext:responseObject];
            [subscriber sendCompleted];
        } failure:^(NSURLSessionDataTask *task, NSError *error) {
            [subscriber sendError:error];
        }];
        return [RACDisposable disposableWithBlock:^{
            if (task.state != NSURLSessionTaskStateCompleted) {
                [task cancel];
            }
        }];
    }];

    RACSignal *title = [fetchData flattenMap:^RACSignal *(NSDictionary *value) {
        if ([value[@"title"] isKindOfClass:[NSString class]]) {
            return [RACSignal return:value[@"title"]];
        } else {
            return [RACSignal error:[NSError errorWithDomain:@"some error" code:400 userInfo:@{@"originData": value}]];
        }
    }];

    RACSignal *desc = [fetchData flattenMap:^RACSignal *(NSDictionary *value) {
        if ([value[@"desc"] isKindOfClass:[NSString class]]) {
            return [RACSignal return:value[@"desc"]];
        } else {
            return [RACSignal error:[NSError errorWithDomain:@"some error" code:400 userInfo:@{@"originData": value}]];
        }
    }];

    RACSignal *renderedDesc = [desc flattenMap:^RACStream *(NSString *value) {
        NSError *error = nil;
        RenderManager *renderManager = [[RenderManager alloc] init];
        NSAttributedString *rendered = [renderManager renderText:value error:&error];
        if (error) {
            return [RACSignal error:error];
        } else {
            return [RACSignal return:rendered];
        }
    }];

    RAC(self.someLablel, text) = [[title catchTo:[RACSignal return:@"Error"]]  startWith:@"Loading..."];
    RAC(self.originTextView, text) = [[desc catchTo:[RACSignal return:@"Error"]] startWith:@"Loading..."];
    RAC(self.renderedTextView, attributedText) = [[renderedDesc catchTo:[RACSignal return:[[NSAttributedString alloc] initWithString:@"Error"]]] startWith:[[NSAttributedString alloc] initWithString:@"Loading..."]];

我们再开发中经常会根据服务器返回的数据解析不同的字段进行不同的操作，上面写的情况在开发中很常见，如果用Charles抓取的话，其实发送了3次请求，都知道这个很不好，我们来分析一下为什么会调用3次呢，我们知道在下面三行代码执行前

 RAC(self.someLablel, text) = [[title catchTo:[RACSignal return:@"Error"]]  startWith:@"Loading..."];
    RAC(self.originTextView, text) = [[desc catchTo:[RACSignal return:@"Error"]] startWith:@"Loading..."];
    RAC(self.renderedTextView, attributedText) = [[renderedDesc catchTo:[RACSignal return:[[NSAttributedString alloc] initWithString:@"Error"]]] startWith:[[NSAttributedString alloc] initWithString:@"Loading..."]];

fetchData、title、desc、renderedDesc都是冷信号，当调用上面三行代码的时候fetchData、title、desc、renderedDesc都变成了热信号了，而title、desc、renderedDesc信号内部都对fetchData信号进行了订阅，从而导致源信号被订阅了3次，而实际上我们只要发送一次网络请求就可以了，即对源信号只有订阅一次就够了。

那我们如何做到对源信号只订阅一次呢，RACSubject的存在就是解决这个问题的。

`RACSubject`闪亮登场

借用一下美团团队提供的一个例子

 RACSubject *subject = [RACSubject subject];
    RACSubject *replaySubject = [RACReplaySubject subject];

    [[RACScheduler mainThreadScheduler] afterDelay:0.1 schedule:^{
        // Subscriber 1
        [subject subscribeNext:^(id x) {
            NSLog(@"Subscriber 1 get a next value: %@ from subject", x);
        }];
        [replaySubject subscribeNext:^(id x) {
            NSLog(@"Subscriber 1 get a next value: %@ from replay subject", x);
        }];

        // Subscriber 2
        [subject subscribeNext:^(id x) {
            NSLog(@"Subscriber 2 get a next value: %@ from subject", x);
        }];
        [replaySubject subscribeNext:^(id x) {
            NSLog(@"Subscriber 2 get a next value: %@ from replay subject", x);
        }];
    }];

    [[RACScheduler mainThreadScheduler] afterDelay:1 schedule:^{
        [subject sendNext:@"send package 1"];
        [replaySubject sendNext:@"send package 1"];
    }];

    [[RACScheduler mainThreadScheduler] afterDelay:1.1 schedule:^{
        // Subscriber 3
        [subject subscribeNext:^(id x) {
            NSLog(@"Subscriber 3 get a next value: %@ from subject", x);
        }];
        [replaySubject subscribeNext:^(id x) {
            NSLog(@"Subscriber 3 get a next value: %@ from replay subject", x);
        }];

        // Subscriber 4
        [subject subscribeNext:^(id x) {
            NSLog(@"Subscriber 4 get a next value: %@ from subject", x);
        }];
        [replaySubject subscribeNext:^(id x) {
            NSLog(@"Subscriber 4 get a next value: %@ from replay subject", x);
        }];
    }];

    [[RACScheduler mainThreadScheduler] afterDelay:2 schedule:^{
        [subject sendNext:@"send package 2"];
        [replaySubject sendNext:@"send package 2"];
    }];

输出

2017-07-03 18:16:02.811 TestObjectProduct[90499:11197356] Subscriber 1 get a next value: send package 1 from subject
2017-07-03 18:16:02.812 TestObjectProduct[90499:11197356] Subscriber 2 get a next value: send package 1 from subject
2017-07-03 18:16:02.812 TestObjectProduct[90499:11197356] Subscriber 1 get a next value: send package 1 from replay subject
2017-07-03 18:16:02.813 TestObjectProduct[90499:11197356] Subscriber 2 get a next value: send package 1 from replay subject
2017-07-03 18:16:02.923 TestObjectProduct[90499:11197356] Subscriber 3 get a next value: send package 1 from replay subject
2017-07-03 18:16:02.923 TestObjectProduct[90499:11197356] Subscriber 4 get a next value: send package 1 from replay subject
2017-07-03 18:16:03.911 TestObjectProduct[90499:11197356] Subscriber 1 get a next value: send package 2 from subject
2017-07-03 18:16:03.911 TestObjectProduct[90499:11197356] Subscriber 2 get a next value: send package 2 from subject
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 3 get a next value: send package 2 from subject
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 4 get a next value: send package 2 from subject
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 1 get a next value: send package 2 from replay subject
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 2 get a next value: send package 2 from replay subject
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 3 get a next value: send package 2 from replay subject
2017-07-03 18:16:03.913 TestObjectProduct[90499:11197356] Subscriber 4 get a next value: send package 2 from replay subject

解释一下这个结果

先分别创建两个信号对象RACSubject和RACReplaySubject，0.1s分别有两个订阅者分别对其订阅；
1s后发送消息，
1. 对于subject
  
  有两个订阅者Subscriber 1和Subscriber 2，所以会先给订阅者发送消息从而有

        ```
        2017-07-03 18:16:02.811 TestObjectProduct[90499:11197356] Subscriber 1 get a next value: send package 1 from subject
        2017-07-03 18:16:02.812 TestObjectProduct[90499:11197356] Subscriber 2 get a next value: send package 1 from subject
        ```
        `subject`内部有个数组会保存订阅者，也就是此时`subject`内部已经有了2个订阅者了
        
2. 对于 `replaySubject`

       也有两个订阅者`Subscriber 1`和`Subscriber 2`，但是她和`subject`不同，它在订阅的时候会首先判断内部之前有没有发送过值，如果有则发送给订阅者
   
        ```
        2017-07-03 18:16:02.812 TestObjectProduct[90499:11197356] Subscriber 1 get a next value: send package 1 from replay subject
        2017-07-03 18:16:02.813 TestObjectProduct[90499:11197356] Subscriber 2 get a next value: send package 1 from replay subject
        
        ```     
        发完以后，`replaySubject`的内部会保存发送的值，也就是`send package 1`，且有两个订阅者。
        
        相信到这里大家没什么问题

1.1s后又多了两个订阅者，Subscriber 3和Subscriber 4；
1. 对于subject，只是保存订阅者；
2. 而当程序走到下面这行的时候
```
```
    [replaySubject subscribeNext:^(id x) {
               NSLog(@"Subscriber 3 get a next value: %@ from replay 
               subject", x);
            }];
```
```
  replaySubject会首先发送之前保存的值也就是send package 1，从而有了
```
2017-07-03 18:16:02.923 TestObjectProduct[90499:11197356] Subscriber 3 get a next value: send package 1 from replay subject
```
3. 然后subject又多了一个订阅者，保存起来；
4. 到这行的时候

    ```
    [replaySubject subscribeNext:^(id x) {
                NSLog(@"Subscriber 4 get a next value: %@ from replay subject", x);
            }];
    ```
    此时的`replaySubject`有一个值`send package 1`，所以有了
    
    ```
    2017-07-03 18:16:02.923 TestObjectProduct[90499:11197356] Subscriber 4 get a next value: send package 1 from replay subject
    ```

2s后subject被订阅，此时subject的订阅者有4个从而

```
2017-07-03 18:16:03.911 TestObjectProduct[90499:11197356] Subscriber 1 get a next value: send package 2 from subject
2017-07-03 18:16:03.911 TestObjectProduct[90499:11197356] Subscriber 2 get a next value: send package 2 from subject
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 3 get a next value: send package 2 from subject
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 4 get a next value: send package 2 from subject

```
`replaySubject`也有4个订阅者

```
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 1 get a next value: send package 2 from replay subject
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 2 get a next value: send package 2 from replay subject
2017-07-03 18:16:03.912 TestObjectProduct[90499:11197356] Subscriber 3 get a next value: send package 2 from replay subject
2017-07-03 18:16:03.913 TestObjectProduct[90499:11197356] Subscriber 4 get a next value: send package 2 from replay subject

```

总结：

RACSubject这个类会保存所有的订阅者，一旦被订阅，就会保存订阅者，等待有值发出的时候，就会告诉所有的订阅者；
RACReplaySubject，是继承RACSubject的所以和RACSubject一样会保存订阅者，然后比父类不同的是它还会保存所有发送过的值，供有新订阅者订阅的时候发送它漏过的值。

如何将一个冷信号转成热信号。

热信号一般在开发中充当的角色如下图所示：

所谓的热信号就是使用RACSubject对象订阅源信号，而其他的订阅者订阅RACSubject

按照上图的理解就有下面的例子

- (void)testSubjectMul {
    RACSignal *signal = [RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        NSLog(@"源信号被订阅了");
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendCompleted];
        return nil;
    }];
    
    RACSubject *subject = [RACSubject subject];
    
    [subject subscribeNext:^(id x) {
        NSLog(@"订阅者1订阅了");
    }];
    
    [subject subscribeNext:^(id x) {
        NSLog(@"订阅者2订阅了");
    }];
    
    [subject subscribeNext:^(id x) {
        NSLog(@"订阅者3订阅了");
    }];
    
    [signal subscribe:subject];
    
}

输出

2017-07-04 22:01:14.443 TestObjectProduct[25044:12106160] 源信号被订阅了
2017-07-04 22:01:14.443 TestObjectProduct[25044:12106160] 订阅者1订阅了
2017-07-04 22:01:14.445 TestObjectProduct[25044:12106160] 订阅者2订阅了
2017-07-04 22:01:14.445 TestObjectProduct[25044:12106160] 订阅者3订阅了

可以看出源信号只被订阅了一次

首先创建源信号；
再创建一个RACSubject信号；
再对RACSubject信号进行订阅
最后RACSubject信号对源信号进行订阅。

当然RACSubject有提供将冷信号变成热信号的遍历方法

- (RACMulticastConnection *)publish;
- (RACMulticastConnection *)multicast:(RACSubject *)subject ;
- (RACSignal *)replay ;
- (RACSignal *)replayLast ; 
- (RACSignal *)replayLazily

我们针对上面的demo分别使用一下

- (RACMulticastConnection *)publish

- (RACMulticastConnection *)publish {
    RACSubject *subject = [[RACSubject subject] setNameWithFormat:@"[%@] -publish", self.name];
    RACMulticastConnection *connection = [self multicast:subject];
    return connection;
}

这个方法没有主动connect，一般和- (RACSignal *)autoconnect搭配使用，每当autoconnect这个信号订阅的时候触发源信号被订阅；

- (void)testSubjectMul {
    RACSignal *signal = [[[RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        NSLog(@"源信号被订阅了");
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendCompleted];
        return nil;
    }] publish] autoconnect];
    
    
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者1订阅了");
    }];
    
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者2订阅了");
    }];
    
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者3订阅了");
    }];
    
   
}

输出

2017-07-04 22:08:05.356 TestObjectProduct[25121:12113364] 源信号被订阅了
2017-07-04 22:08:05.356 TestObjectProduct[25121:12113364] 订阅者1订阅了

这里为什么只会有订阅者1执行了，是因为autoconnect只允许connect一次，后面执行的只是保存了订阅者，以便下次执行使用。

- (RACMulticastConnection *)multicast:(RACSubject *)subject

- (void)testSubjectMul {
    RACSignal *signal = [RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        NSLog(@"源信号被订阅了");
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendCompleted];
        return nil;
    }];
    
    RACSubject *subject = [RACSubject subject];
    
    RACMulticastConnection *connect  =   [signal multicast:subject];
    
    [subject subscribeNext:^(id x) {
        NSLog(@"订阅者1订阅了");
    }];
    
    [subject subscribeNext:^(id x) {
        NSLog(@"订阅者2订阅了");
    }];
    
    [subject subscribeNext:^(id x) {
        NSLog(@"订阅者3订阅了");
    }];
    
    [connect connect];
    
   
}

输出

017-07-04 22:12:26.846 TestObjectProduct[25180:12117807] 源信号被订阅了
2017-07-04 22:12:26.846 TestObjectProduct[25180:12117807] 订阅者1订阅了
2017-07-04 22:12:26.846 TestObjectProduct[25180:12117807] 订阅者2订阅了
2017-07-04 22:12:26.846 TestObjectProduct[25180:12117807] 订阅者3订阅了

- (RACSignal *)replay

- (void)testSubjectMul {
    RACSignal *signal = [[RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        NSLog(@"源信号被订阅了");
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendCompleted];
        return nil;
    }] replay];
    
   
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者1订阅了");
    }];
    
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者2订阅了");
    }];
    
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者3订阅了");
    }];
    
   
}

输出

2017-07-04 22:14:22.805 TestObjectProduct[25224:12120354] 源信号被订阅了
2017-07-04 22:14:22.805 TestObjectProduct[25224:12120354] 订阅者1订阅了
2017-07-04 22:14:22.806 TestObjectProduct[25224:12120354] 订阅者2订阅了
2017-07-04 22:14:22.806 TestObjectProduct[25224:12120354] 订阅者3订阅了

这个一调用replay的时候就对源信号订阅了，只不过当时没有订阅者，由于内部使用的是RACReplaySubject对象，此时会保存发送的值，等到订阅者订阅的时候就会发送保存的值了

比如稍微改一下

- (void)testSubjectMul {
    RACSignal *signal = [[RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        NSLog(@"源信号被订阅了");
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendCompleted];
        return nil;
    }] replay];
    
   
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者1订阅了");
    }];
    
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者2订阅了");
    }];
    
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者3订阅了");
    }];
    
   
}

就会输出

2017-07-04 22:17:06.612 TestObjectProduct[25277:12124611] 源信号被订阅了
2017-07-04 22:17:06.613 TestObjectProduct[25277:12124611] 订阅者1订阅了
2017-07-04 22:17:06.613 TestObjectProduct[25277:12124611] 订阅者1订阅了
2017-07-04 22:17:06.613 TestObjectProduct[25277:12124611] 订阅者2订阅了
2017-07-04 22:17:06.613 TestObjectProduct[25277:12124611] 订阅者2订阅了
2017-07-04 22:17:06.614 TestObjectProduct[25277:12124611] 订阅者3订阅了
2017-07-04 22:17:06.614 TestObjectProduct[25277:12124611] 订阅者3订阅了

- (RACSignal *)replayLast

- (void)testSubjectMul {
    RACSignal *signal = [[RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        NSLog(@"源信号被订阅了");
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendNext:@"假设这是另一个网络"];
        [subscriber sendCompleted];
        return nil;
    }] replayLast];
    
   
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者1订阅了--%@",x);
    }];
    
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者2订阅了--%@",x);
    }];
    
    [signal subscribeNext:^(id x) {
        NSLog(@"订阅者3订阅了--%@",x);
    }];
    
   
}

输出

2017-07-04 22:19:52.137 TestObjectProduct[25395:12129467] 源信号被订阅了
2017-07-04 22:19:52.138 TestObjectProduct[25395:12129467] 订阅者1订阅了--假设这是另一个网络
2017-07-04 22:19:52.138 TestObjectProduct[25395:12129467] 订阅者2订阅了--假设这是另一个网络
2017-07-04 22:19:52.138 TestObjectProduct[25395:12129467] 订阅者3订阅了--假设这是另一个网络

这个和replay类似，唯一的不同就是replay保存所以发送过的值，而它保存的是最新的发送的值

- (RACSignal *)replayLazily

这个要和replay对比看，replay方法是即使没有订阅者，源信号也会被订阅，而replayLazily只有当返回的信号被订阅的时候源信号才会被订阅，先看replay

- (void)testSubjectMul {
    RACSignal *signal = [[RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        NSLog(@"源信号被订阅了");
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendNext:@"假设这是另一个网络"];
        [subscriber sendCompleted];
        return nil;
    }] replay];

输出

2017-07-04 22:24:02.298 TestObjectProduct[25558:12136590] 源信号被订阅了

再看replayLazily，先看她没有被订阅

- (void)testSubjectMul {
    RACSignal *signal = [[RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        NSLog(@"源信号被订阅了");
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendNext:@"假设这是另一个网络"];
        [subscriber sendCompleted];
        return nil;
    }] replayLazily];    
   
}

输出

无

再看被订阅了

- (void)testSubjectMul {
    RACSignal *signal = [[RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        NSLog(@"源信号被订阅了");
        [subscriber sendNext:@"假设这是网络"];
        [subscriber sendNext:@"假设这是另一个网络"];
        [subscriber sendCompleted];
        return nil;
    }] replayLazily];    
   [signal subscribeNext:^(id x) {
        NSLog(@"订阅者1订阅了--%@",x);
    }];
}

输出

2017-07-04 22:26:56.527 TestObjectProduct[25601:12139422] 源信号被订阅了
2017-07-04 22:26:56.528 TestObjectProduct[25601:12139422] 订阅者1订阅了--假设这是网络
2017-07-04 22:26:56.528 TestObjectProduct[25601:12139422] 订阅者1订阅了--假设这是另一个网络

说道这里我们可以修改一下开始那个网络请求了

 self.sessionManager = [[AFHTTPSessionManager alloc] initWithBaseURL:[NSURL URLWithString:@"http://api.xxxx.com"]];

    self.sessionManager.requestSerializer = [AFJSONRequestSerializer serializer];
    self.sessionManager.responseSerializer = [AFJSONResponseSerializer serializer];

    @weakify(self)
    RACSignal *fetchData = [[RACSignal createSignal:^RACDisposable *(id<RACSubscriber> subscriber) {
        @strongify(self)
        NSURLSessionDataTask *task = [self.sessionManager GET:@"fetchData" parameters:@{@"someParameter": @"someValue"} success:^(NSURLSessionDataTask *task, id responseObject) {
            [subscriber sendNext:responseObject];
            [subscriber sendCompleted];
        } failure:^(NSURLSessionDataTask *task, NSError *error) {
            [subscriber sendError:error];
        }];
        return [RACDisposable disposableWithBlock:^{
            if (task.state != NSURLSessionTaskStateCompleted) {
                [task cancel];
            }
        }];
    }] replayLazily];//只要加一个这个就可以了

    RACSignal *title = [fetchData flattenMap:^RACSignal *(NSDictionary *value) {
        if ([value[@"title"] isKindOfClass:[NSString class]]) {
            return [RACSignal return:value[@"title"]];
        } else {
            return [RACSignal error:[NSError errorWithDomain:@"some error" code:400 userInfo:@{@"originData": value}]];
        }
    }];

    RACSignal *desc = [fetchData flattenMap:^RACSignal *(NSDictionary *value) {
        if ([value[@"desc"] isKindOfClass:[NSString class]]) {
            return [RACSignal return:value[@"desc"]];
        } else {
            return [RACSignal error:[NSError errorWithDomain:@"some error" code:400 userInfo:@{@"originData": value}]];
        }
    }];

    RACSignal *renderedDesc = [desc flattenMap:^RACStream *(NSString *value) {
        NSError *error = nil;
        RenderManager *renderManager = [[RenderManager alloc] init];
        NSAttributedString *rendered = [renderManager renderText:value error:&error];
        if (error) {
            return [RACSignal error:error];
        } else {
            return [RACSignal return:rendered];
        }
    }];

    RAC(self.someLablel, text) = [[title catchTo:[RACSignal return:@"Error"]]  startWith:@"Loading..."];
    RAC(self.originTextView, text) = [[desc catchTo:[RACSignal return:@"Error"]] startWith:@"Loading..."];
    RAC(self.renderedTextView, attributedText) = [[renderedDesc catchTo:[RACSignal return:[[NSAttributedString alloc] initWithString:@"Error"]]] startWith:[[NSAttributedString alloc] initWithString:@"Loading..."]];

最后编辑于：2017.12.08 10:05:59

人面猴
序言：七十年代末，一起剥皮案震惊了整个滨河市，随后出现的几起案子，更是在滨河造成了极大的恐慌，老刑警刘岩，带你破解...
沈念sama阅读 202,723评论 5赞 476
死咒
序言：滨河连续发生了三起死亡事件，死亡现场离奇诡异，居然都是意外死亡，警方通过查阅死者的电脑和手机，发现死者居然都...
沈念sama阅读 85,080评论 2赞 379
救了他两次的神仙让他今天三更去死
文/潘晓璐我一进店门，熙熙楼的掌柜王于贵愁眉苦脸地迎上来，“玉大人，你说我怎么就摊上这事。” “怎么了？”我有些...
开封第一讲书人阅读 149,604评论 0赞 335
道士缉凶录：失踪的卖姜人
文/不坏的土叔我叫张陵，是天一观的道长。经常有香客问我，道长，这世上最难降的妖魔是什么？我笑而不...
开封第一讲书人阅读 54,440评论 1赞 273
港岛之恋（遗憾婚礼）
正文为了忘掉前任，我火速办了婚礼，结果婚礼上，老公的妹妹穿的比我还像新娘。我一直安慰自己，他们只是感情好，可当我...
茶点故事阅读 63,431评论 5赞 364
恶毒庶女顶嫁案：这布局不是一般人想出来的
文/花漫我一把揭开白布。她就那样静静地躺着，像睡着了一般。火红的嫁衣衬着肌肤如雪。梳的纹丝不乱的头发上，一...
开封第一讲书人阅读 48,499评论 1赞 281
城市分裂传说
那天，我揣着相机与录音，去河边找鬼。笑死，一个胖子当着我的面吹牛，可吹牛的内容都是我干的。我是一名探鬼主播，决...
沈念sama阅读 37,893评论 3赞 395
双鸳鸯连环套：你想象不到人心有多黑
文/苍兰香墨我猛地睁开眼，长吁一口气：“原来是场噩梦啊……” “哼！你这毒妇竟也来了？” 一声冷哼从身侧响起，我...
开封第一讲书人阅读 36,541评论 0赞 256
万荣杀人案实录
序言：老挝万荣一对情侣失踪，失踪者是张志新（化名）和其女友刘颖，没想到半个月后，有当地人在树林里发现了一具尸体，经...
沈念sama阅读 40,751评论 1赞 296
护林员之死
正文独居荒郊野岭守林人离奇死亡，尸身上长有42处带血的脓包…… 初始之章·张勋以下内容为张勋视角年9月15日...
茶点故事阅读 35,547评论 2赞 319
白月光启示录
正文我和宋清朗相恋三年，在试婚纱的时候发现自己被绿了。大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
茶点故事阅读 37,619评论 1赞 329
活死人
序言：一个原本活蹦乱跳的男人离奇死亡，死状恐怖，灵堂内的尸体忽然破棺而出，到底是诈尸还是另有隐情，我是刑警宁泽，带...
沈念sama阅读 33,320评论 4赞 318
日本核电站爆炸内幕
正文年R本政府宣布，位于F岛的核电站，受9级特大地震影响，放射性物质发生泄漏。R本人自食恶果不足惜，却给世界环境...
茶点故事阅读 38,890评论 3赞 307
男人毒药：我在死后第九天来索命
文/蒙蒙一、第九天我趴在偏房一处隐蔽的房顶上张望。院中可真热闹，春花似锦、人声如沸。这庄子的主人今日做“春日...
开封第一讲书人阅读 29,896评论 0赞 19
一桩弑父案，背后竟有这般阴谋
文/苍兰香墨我抬头看了看天上的太阳。三九已至，却和暖如春，着一层夹袄步出监牢的瞬间，已是汗流浃背。一阵脚步声响...
开封第一讲书人阅读 31,137评论 1赞 259
情欲美人皮
我被黑心中介骗来泰国打工，没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留，地道东北人。一个月前我还...
沈念sama阅读 42,796评论 2赞 349
代替公主和亲
正文我出身青楼，却偏偏与公主长得像，于是被迫代替她去往敌国和亲。传闻我的和亲对象是个残疾皇子，可洞房花烛夜当晚...
茶点故事阅读 42,335评论 2赞 342

RAC的冷信号和热信号-RACSubject

RAC的冷信号和热信号

何为冷信号，热信号？

为何会有RACSubject这个类的存在？

RACSubject闪亮登场

如何将一个冷信号转成热信号。

推荐阅读更多精彩内容

为何会有`RACSubject`这个类的存在？

`RACSubject`闪亮登场