Why does autoupdate use DDP?


#1

DDP is awesome and all, but why is it used in the case of hot code push?

It seem’s like an alternative would be to have the client code in a pure ‘GET’ able form, independent from node.

How this would look:
Allow the ‘GET’ of a client manifest, detect if any files changed. If any changed, fetch them and potentially run the update. DDP could still be used to force new request of the client application, and still achieve fast reloads.

What it would accomplish:
This would allow hosting of the client version of the meteor application on more easily scaled static file storage, as well as meaning entirely static meteor applications are now possible.

Is my understanding of this correct?