Difference between revisions of "Template:CreditLine Programming Rules"
From Payment Processing Software Library
Line 7: | Line 7: | ||
instance 1 gets TERM001, and instance 2 gets TERM002. | instance 1 gets TERM001, and instance 2 gets TERM002. | ||
− | 4. Some environments, such as VB.NET may loose the automation reference if the same API is called twice too quickly. Avoid calling the same API in '''tight loops''' | + | 4. Some environments, such as VB.NET may loose the automation reference if the same API is called twice too quickly. Avoid calling the same API in '''tight loops''' - add a reasonable delay if needed. |
5. Avoid '''redundant''' and '''inefficient''' code. | 5. Avoid '''redundant''' and '''inefficient''' code. |
Revision as of 15:05, 17 May 2006
1. Each instance needs to call the initialization function (such as clcInit or Init) themselves and get a unique handle to themselves. This handle can not be shared.
2. Each instance can only make one request at a time, but one process can have multiple instances to make multiple requests.
3. Each instance needs to have a unique client name. For example, instance 1 gets TERM001, and instance 2 gets TERM002.
4. Some environments, such as VB.NET may loose the automation reference if the same API is called twice too quickly. Avoid calling the same API in tight loops - add a reasonable delay if needed.
5. Avoid redundant and inefficient code.