On 9/4/05, Manoj Prakash <[EMAIL PROTECTED]> wrote: > Yes, I haven't disabled caching. > > In our tests, we have seen tapestry doing pretty well if client is on > same network as server. > > We start to see the perf issue when: > 1. clients are on a separate network than the server, and in such cases; > tapestry/tomcat log indeed says that it is taking as much time.
That sounds like a DNS issue. Maybe something in the application or in tomcat is doing a reverse dns resolution which can be long? Henri. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
