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.
I'm annoyed at the slower startup speed. HiveMind 1.2 will include new, non-XML ways to construct services that will use much less reflection. I've found that runtime performance "feels" about the same. On 8/19/05, Kent Tong <[EMAIL PROTECTED]> wrote: > Hi, > > The latency of a Tapestry 4 app when processing the first request > is significantly longer than a Tapestry 3 one. This is significantly > affecting the efficiency of development. > > I suspect this is because of the huge amount of processing needed to > process the hivemind services and configurations. Is this true? > It seems that this work is done when constructing the hivemind registry. > In that case, is it possible to construct the registry bit by bit on > demand? For example, if I'm not getting access to a certain service, > there is no need to parse the service point nor create the proxy and > etc. > > -- > Author of e-book for learning Tapestry (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]
