You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We shouldn't have to put stub vat-comms.js or vat-vattp.js files into basedirs to create the comms layer. Instead there should just be some config flag that says "yes I want comms" and it should make the necessary vats (using standardized names so the bootstrap code can wire them up correctly).
It might be nice to wire up the comms and vattp vats automatically too. Doing that will reduce the amount of boilerplate in bootstrap.js, leaving just the initial ingress/egress calls (which we should find a way to simplify too).
The text was updated successfully, but these errors were encountered:
I don't think so. Leaving it open as there's work to do to make creation of these vats happen by default the way we now do with the vatAdmin vat and device.
We shouldn't have to put stub
vat-comms.js
orvat-vattp.js
files into basedirs to create the comms layer. Instead there should just be someconfig
flag that says "yes I want comms" and it should make the necessary vats (using standardized names so the bootstrap code can wire them up correctly).It might be nice to wire up the comms and vattp vats automatically too. Doing that will reduce the amount of boilerplate in
bootstrap.js
, leaving just the initial ingress/egress calls (which we should find a way to simplify too).The text was updated successfully, but these errors were encountered: