Kbase P98217: What are the new performance improvements for the DynLookups and DynCombos in Dynamics 2.1B
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/06/2005 |
|
Status: Unverified
GOAL:
What are the new performance improvements for the DynLookups and DynCombos in Dynamics 2.1B
GOAL:
How to use the new DynCombo/DynLookup API
GOAL:
What is the new class hierarchy for the DynCombo/DynLookup
GOAL:
What is the new keep_old_field_API session property
GOAL:
What is the new field_cache_options session property
FACT(s) (Environment):
Dynamics 2.1B
FIX:
The following are the performance improvements for DynLookups/DynCombos introduced in Dynamics 2.1B:
-Improve data management
Centralize the Combo/Lookup temp-tables with handle references made available to all interested parties when required. Develop a new set of APIs that use this single copy of the temp-tables
-Reduce the number of AppServer requests
AppServer calls to retrieve data are encapsulated by the Lookup class. This allow for the pre-processing of data that are passed to the server-side procedure to be as efficient as possible.
-Reduce the size of data in AppServer requests
-New Session Parameters
-- keep_old_field_API: Valid Values: YES/NO. Indicates which API to use. If it is not defined for a specific Session Type, the default is NO, meaning that the NEW API will be used.
-- field_cache_options: Valid values: ALL | <FieldClass>[,<FieldClass>]|<empty>. If this property is not defined or its value is blank NO caching of SDFs will occur.
-New Class Structure
The new class LookupField was introduced to manage the DynCombo/DynLookup temp-tables, remove code duplication, and incorporate common data caching functionality. The LookupField class will be a superclass of DynCombo and DynLookup and a subclass of Field.
-New API
The current events and their corresponding APIs, getLookupQuery, getComboQuery, displayCombo, and displayLookup will be replaced with their parameter-less equivalents: prepareField, displayField. There is no need to have different events for Lookups and Combos.
A number of other APIs will also be deprecated in favor of a new, thinner implementation.
The existing APIs would be marked as deprecated but will be maintained for a specified period of time to allow for the migration of customer applications.