Jim Garlick

When we discussed this before, I think a new "grow" interface was proposed but maybe that is out of scope for RFC 20?

A fragment would contain all the resources allocated to the job on one or more execution targets (broker ranks). That is, it would not be further subdivided. One thought on...

See flux-framework/rfc#427 for a proposed protocol.

Do we have a maximum value size other than the maximum content blob size?

> The dumb approach would be some `const char *mod_dependency` comma separated string or similar array of sorts. I think modules declaring variables for access using `dlsym()` is a problem...

> I guess the advantage is disconnect / ENODATA is an automatic "module unloaded" Right. Less code!

I figured the client side would be wrapped up in a single function that modules could optionally call to increment the reference count on another module/service. That function might have...