[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[virgo-dev] Slow startup, deploying "transitively complete" applications, custom deployer howto
- From: Peter Gardfjäll <peter.gardfjell@xxxxxxxxx>
- Date: Wed, 2 Jun 2010 19:51:15 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=UXxNtXTDApNZOGzAZRTuDqxxfFi2tWQZdTgCCf/9QjcJecrJo0kU/dlGLKXRKXzqnb HuuGWl0DiJBfFL9iKOOaQe8wXRs6W15KIYX3ZKF7qfHNCV0t8cgtSS6CNv4Lwg9U9yNa 5DnxHM/P7r6MW5nlMyV21c+XvzJyz9bMQgInI=
I've made a couple of posts on the forum thread
without receiving a reply.
Maybe my posts have passed unnoticed (or could the poor response be
due to lack of interest?).
Anyhow, I thought I'd try my luck on the mailing list instead.
Basically I have three questions:
(1) Has there been any progress in investigating the "slow startup issue"?
(2) Also, Glyn, in the original forum thread (at Spring dm,
you mentioned ideas about providing support for deploying
"transitively complete" applications/subsystems. Is this on Virgo's
(3) Finally, I assume that it is possible to hook in additional
deployers (handling new types of deployment artifacts) in Virgo. If
this is the case, I'd appreciate any pointers on how to get started
(what interfaces need to be implemented, what design guidelines should
be adhered to, etc)?