Alex

> I could reasonably complain if this function sometimes works and sometimes doesn't, If you know/understand how things work they always will be working that way, if you don't they...

When hot stream completes - that means it's dead, it's over, it ain't going any further, nothing can "resume" completed stream, just restart all over again.

> Now, when all the subscribers unsubscribe, the stream knows the latest computed value. I believe it is expected. After there no subscriptions anymore a stream actually completes (and "forgets"...

@laszlokorte well I believe to say about "side effects" correspondece with HTTP methots is not appropriate, performing any HTTP request is side effect regardless of method or other request details....

It is obviously a side affect any way, regardles of what in request itself. But I think that this whole aproach breaks cycle like this does https://github.com/cyclejs/core/issues/268 regardles if it...

@milankinen `hooks` it is already not trivial) I mean not difficult but it adds exessive (and some kind of monkey pathing) code, such mapping it could be done this way...

> You need to define what is the "external world" and what is the "application". It's pretty clear that graphics and mouse inputs are from the external world, but so...

> One-time read-only GET requests are one type of pull API that works because of the laziness in Rx subscribe, but how can we get a nice pull API for...

@ronag it seems that it turns to be a disscussion about allowing HTTP driver to emulate/imitate (not sure about word) push source behaviour.

Just as current workaround with webpack it can be fixed by using: ```ts new webpack.NormalModuleReplacementPlugin( /snabbdom\/[^\/]*$/, (resource) => { resource.request = resource.request.replace(/snabbdom\//, 'snabbdom/es/' ) }) ```