Kbase 16838: Why File View ( Project ) locks an agent
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Why File View ( Project ) locks an agent
Why Progress locks an agent in Files View
-----------------------------------------
Two reasons why Webspeed 2.0 locks an agent in Files
(known as Project in Beta 1) View are for context and performance.
When the list of directories and files first appear, Progress
builds a temp-table of the directory/file structure with the
'state' of the display, i.e. are directories expanded or collapsed
and has the user supplied a filter? Initially, all directories
are collapsed. A user might click on a directory to expand it.
Rather than rebuild the entire display, Progress only rebuilds
the list of sub-directories and files in the directory the user
clicked on. Hence the performance implication. The locked agent
enables Progress to maintain context of the directory display.
Another side of context is the fact that users can open multiple
files in Workshop and work on them over multiple web requests.
Without a locked agent, the 'state' of the Web object the user edits
would be lost after every POST to the web server.
Progress Software Technical Support Note # 16838