Understanding the expected behaviour of MeteorObservable.call() about meteor-rxjs HOT 2 CLOSED

For anyone else interested... for now I have implemented the following which meets my needs:

import { MeteorObservable } from 'meteor-rxjs';
import { Observable, Subject } from 'rxjs';

export class MeteorObservableOnce extends MeteorObservable {

    public static call<T>(name: string, ...args: any[]): Observable<T> {
        let subject: Subject<T> = new Subject();
        super.call.apply(this, arguments).subscribe(subject);
        return subject.asObservable();
    }

}

You could just as easily give the method another name and still keep access to the original call method

from meteor-rxjs.

It seems my understanding of Observables was limited and the reason it has been done this way (as a 'cold Observable') is because there is no guarantee that subscribers won't miss the first data received from the server if the call is made before the subscribers are attached. However unlikely it might be that data will be 'lost' considering the delay in receiving data over the wire it still cannot be guaranteed.

The way to go is probably to create a ConnectableObservable and work with that. For future reference here is a link to an excellent post about the difference between hot & cold Observables:

https://blog.thoughtram.io/angular/2016/06/16/cold-vs-hot-observables.html

from meteor-rxjs.