Re: acme sac
> The one from http://caerwyn.com/acme/ is great. Thanks Caerwyn.
All I was expecting was maybe emu.exe + acme.dis or so,
not so much as we get now.
> I found it takes long long time to fire up it though.
> Is that only me seeing this?
For me it definitely does not run instantly,
but neither does it take an extremely long time to start.
I'm sorry to change topic here, but:
Now that I've seen this I can rephrase my question about deployment
(I asked a while ago).
I guess my question is about granularity: can I package indivual
end-user applications in separate self-contained packages,
and still let them cooperate when they are run concurrently?
Suppose that, next to acme, I also want to package charon
in the same way.
And then I start acme, and I start charon, and I get two
instances of emu (I guess).
Is it then possible to plumb http refs from acme to charon?
Where would my plumber be, in the acme emu or the charon emu,
or would I have two plumbers that 'know' each other?
Can I configure the plumber that runs in the 'acme' emu
such that, when no charon is running, it will start the