Module-file format (DRAFT)

[Mark Reinhold]

> Date: Tue, 19 Jan 2010 18:07:04 +0000
> From: alan.bateman at sun.com

> The format seem straight-forward. One thing that isn't completely clear (to me
> anyway) is how does one recognize the end of a section that contains several
> named files? In the following, for example, how do I know distinguish a new
> section header from another SectionFileHeader?
> 
> SectionHeader
>  type = NATIVE_LIBS
> SectionFileHeader
>  usize = 50k, name = libfoo.so
> [libfoo.so]
> SectionSize

(I think you mean SectionFileHeader here.)

>  usize = 70k, name = libbar.so
> [libbar.so]
> SectionHeader
>  type = CLASSES
> :

Good question -- you can't.

I've added a u2 type field to SectionFileHeader so that this is possible.

> I agree with Alex's comment that u4 might not be sufficient for the compressed
> or uncompressed size.

Fixed.

> Is the intention that a module can be launched/started before it is fully
> transferred/"installed"

No.  An application that needs to (appear to) start quickly should be
structured as a small launch module with optional dependences upon its
other modules.  (This is just as in JNLP today.)  We'll eventually come
up with a way to label such dependences so that they'll be downloaded
and installed right after the launch module.

- Mark