Add documentation to "Kefir.pool" as "Rx.Subject equivalent" about kefir

[rpominov]

Actually in Kefir all observables support multiple subscribers. In your example it might seem otherwise because your stream emits events synchronously, meaning there's no delay between activation (first subscription) and emitting all events. So first subscriber receives the events, but by the time you add a second one they are already emitted.

If your stream looked like this:

let s = Kefir.stream(obs=>{
  let i = 0;
  const intervalIt = setInterval(() => {obs.emit(i); i++})
  return () => {
    clearInterval(intervalId);
  }
})

Then you could do the following and both subscribers would get the events:

s.onValue(v=>{
  console.log('+++++ value',v)
}) //1st subscriber

s.observe(v=>{
  console.log('----- value',v)
}) //2nd subscriber

More on it here https://kefirjs.github.io/kefir/#current-in-streams

[abrakadobr]

Nice, thanks for explanation. =)
So, I'm using streams almost everywhere, and like "can't guarantee" - my streams will require async, or not (basically, thats why i'm useing streams - they unify for me sync/async), so pool gives me like "guarantied solution" for some situations, when sources can be syncronous and i need deliver event to multiple subscibers (and "end" is not required, ofc)

So, may be point somehow this behavor in docs?