Re: Module naming and identification
Mark Miller <[email protected]>
| Newsgroups | gmane.comp.lang.e.general |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Apr 15, 2009 at 10:56 AM, Lex Spoon <[email protected]> wrote: > For deployment, there are a couple of easy choices. The simplest is > to bundle > up the entire app, complete with all dependencies, and stick it in a > directory > whose name includes a hash of the entire app's content. This > approach means there > is still no compiler or other tool. Better, though, would be to scan > the code for module > references and pick a specific version for each one. Then, dump all > of these > module references into a single JSON map going from module name to > module version. This JSON map could be included in the initial app > download, > and it can be consulted as part of the implementation of require(). > > Given this general scheme of deployment, it's an additional > requirement that the > module references be statically analyzable. Hi Lex, something about the way you put things here shook loose an old dormant memory of an old e-lang thread "Anonymous Unspoofable Cyclic Distributed Static Linking": http://www.eros-os.org/pipermail/e-lang/2000-January/003188.html http://www.eros-os.org/pipermail/e-lang/2000-January/003194.html http://www.eros-os.org/pipermail/e-lang/2000-January/003196.html http://www.eros-os.org/pipermail/e-lang/2000-January/003197.html -- Text by me above is hereby placed in the public domain Cheers, --MarkM