[rxjs] Shares a single subscription -- publish()

If have an observable and you subscribe it twice, those tow subscritions have no connection. 

复制代码
console.clear();
var Observable = Rx.Observable;
var _id = 1;

var source = Observable.create(function(Observe){
  var myId = _id++;
  Observe.onNext('Observable ' + myId);
  setTimeout(function(){
    Observe.onNext('Observable... ' + myId);
    Observe.onCompleted();
  }, 1000);
});

var subscrition1 = source.subscribe(function onNext(x){
  console.log('Observable 1: ' + x);
});

var subscrition2 = source.subscribe(function onNext(x){
  console.log('Observable 2: ' + x);
});
复制代码

Result:

/*"Observable 1: Observable 1"
"Observable 2: Observable 2"
"Observable 1: Observable... 1"
"Observable 2: Observable... 2"*/

 

publish():

Returns an observable sequence that is the result of invoking the selector on a connectable observable sequence that shares a single subscription to the underlying sequence.

复制代码
console.clear();
var Observable = Rx.Observable;
var _id = 1;

var source = Observable.create(function(Observe){
  var myId = _id++;
  Observe.onNext('Observable ' + myId);
  setTimeout(function(){
    Observe.onNext('Observable... ' + myId);
    Observe.onCompleted();
  }, 1000);
});
var published = source.publish();

var subscrition1 = published.subscribe(function onNext(x){
  console.log('Observable 1: ' + x);
});

var subscrition2 = published.subscribe(function onNext(x){
  console.log('Observable 2: ' + x);
});

var connection = published.connect();
复制代码

Results:

/*
"Observable 1: Observable 1"
"Observable 2: Observable 1"
"Observable 1: Observable... 1"
"Observable 2: Observable... 1"
*/

You can see the result just have one single subscrition then.

 

You can dispose the connection:

connection.dispose();

Results:

/*"Observable 1: Observable 1"
"Observable 2: Observable 1"*/

 

There is a problem when you connect the published observables at different place.

复制代码
var Observable = Rx.Observable;
var _id = 1;

var source = Observable.create(function(Observe){
  var myId = _id++;
  Observe.onNext('Observable ' + myId);
  setTimeout(function(){
    Observe.onNext('Observable... ' + myId);
    Observe.onCompleted();
  }, 1000);
});
var published = source.publish();
var connection = published.connect();

var subscrition1 = published.subscribe(function onNext(x){
  console.log('Observable 1: ' + x);
});

var subscrition2 = published.subscribe(function onNext(x){
  console.log('Observable 2: ' + x);
});

//var connection = published.connect();
复制代码

Results:

/*"Observable 1: Observable... 1"
"Observable 2: Observable... 1"*/

If we move the connect() funciton up before subscribe(). Then we missed the very first console.log(); It means connection is already start, but no one subscribe it yet.

 

Therefore, we don't use publish() funciton alone, more than often we use publish().refCount() function together.

posted @   Zhentiw  阅读(341)  评论(0编辑  收藏  举报
(评论功能已被禁用)
编辑推荐:
· SQL Server 2025 AI相关能力初探
· Linux系列:如何用 C#调用 C方法造成内存泄露
· AI与.NET技术实操系列(二):开始使用ML.NET
· 记一次.NET内存居高不下排查解决与启示
· 探究高空视频全景AR技术的实现原理
阅读排行:
· 阿里最新开源QwQ-32B,效果媲美deepseek-r1满血版,部署成本又又又降低了!
· Manus重磅发布:全球首款通用AI代理技术深度解析与实战指南
· 开源Multi-agent AI智能体框架aevatar.ai,欢迎大家贡献代码
· 被坑几百块钱后,我竟然真的恢复了删除的微信聊天记录!
· AI技术革命,工作效率10个最佳AI工具
点击右上角即可分享
微信分享提示