forum home | register | profile | members |search | faq
homepage | lost password? | chat room
|
|
QSA ToolWorks Public Feedback Forum forum home | register | profile | members |search | faq homepage | lost password? | chat room |
| QSA ToolWorks Public Feedback Forum > General Helix Talk > Hot or Cold Forms | You are not logged in. Login or Register. |
| Pages: 1 |
|
| Author: | Topic: Hot or Cold Forms | |||
lucidlee Posts: 18 Registered: 2003-04-09    |
 Posted: Aug 23, 2003 11:05:39 am    
I'm wondering if we can't better control over the usage of hot and cold forms. In particular, I usually design multi-user databases with all hot forms and then (reluctantly) cool those that cause too much trouble. In earlier versions of Helix (I don't know if its curently the case) a user with a list open would see it redrawn every time a record on it was edited elsewhere on the network. And if two users had the same form open and editing a record one would have their record blanked out if the other entered their data first. The obvious solution in each case is to make the forms cold so that they are not immediately refreshed. But its easy to devise situations where you don't want this to happen. For example, a busy reservations system could not afford to have stale data on show if it meant misallocation of a seat or appointment. The same problem encountered in Browsers where the entire form has to be redrawn even if only one field has changed. The solution is the same reduce the granularity of the update so that individual fields can be redrawn at will and thus can be marked as hot or cold. Perhaps this granularity can be controlled via a calculation as well so that an update remains cold unless the change is above a threshold value. Or perhaps it can be controlled by the way the update occurs. For example if the update was the result of particular Post , Field(s), View or Sequence. Lee
|
| Pages: 1 |
|
| Lost Password? Powered by UPB Version : 1.8 A script by PHP Outburst |
