Yes, and that's exactly what's happening inside HiveMind. However, starting up (processing the first request) requires a huge amount of initialization. The first request "flows" over, say, 60% of the code base.
On 8/19/05, Kent Tong <[EMAIL PROTECTED]> wrote: > Howard Lewis Ship <hlship <at> gmail.com> writes: > > > HiveMind is something of an all-or-nothing approach, by design. > > Because modules contribute information to other modules, you can't get > > by with an incremental approach. > > Sorry, I don't understand. The registry could load and parse all > the module descriptors at startup for fast lookup without creating > proxies or parsing contributions. Only when someone asks me for > a service or a configuration, then I would do the real work. > > -- > Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
