I still don't trust the tally completely because i only se the time of the
WebApplication I first refresh and not both apps as I would expect.
JM> As you know in Aida we have a two step building a response to the request:
JM> 1. composing a page to build a tree of web elements
JM> 2. streaming that tree as HTML back to the web browser
JM> So, when we'll need some speedup of Aida, we should tackle the second
JM> part of the story. But so far I didn't see much need for such speedup.
In one of my jobs I still do assembler so I cannot keep my hands off a
profiler :-) Professional disease. For my own purpose I think it's too
early for optimising.
JM> What do others thinks? Anyone in need for such optimizations?
If I would need to speed it up I would try to to cache the html stream
and only copy together pieces.
Something along the lines: Each web element should know if it (or its
model?) changed. If unchanged only return a copy of its cached stream
contents. Otherwise do the normal thing.
So if only one entry in a WebGrid changed all but one would just put
their cached html into the stream. In a next step this could be done
hierarchically, so the table would know, none of its elements changed
and just copy its own cache. If the refresh button were pressed the
whole WebPage would just return its cache.
Hey, I talk about things I don't know enough about :-))
Herbert mailto:[hidden email]
Aida mailing list