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]
