About the new upload-control, this is what a decent 'wire-value' for it
looks like:
{
id: "key-random-string", // temp-store-identification-key,
// indirectly points to ref at
// service:/upload/{id}/data
ref: "/path/to-download, // points to download uri
size: 29304, // value in bytes - optional
filename: "somename.ext", // a visible name
mimetype: "text/plain" // info about type
}
size, filename and mimetype are purely informational
either id or ref should be present.
if ref is set then the data is considered to be persistent and managed
by the server: no removal nor life-checking is going to be performed
from the control
unlike if not set: then id is used to communicate to the temp-store for
exactly those actions (removal/keep alive)
-marc=
