|
version 1.1.2.11, 2013/09/29 20:51:12
|
version 1.1.2.12, 2013/10/03 10:45:31
|
|
|
|
| pull not completed so we feed the responses back to the EnmerationContext | pull not completed so we feed the responses back to the EnmerationContext |
| queues | queues |
| 3. Lots of minor TODOs, diagnostics, etc. | 3. Lots of minor TODOs, diagnostics, etc. |
| 4. External runtime variables. Decide this as part of PEP. The variables |
4. External runtime variables. Proposing that they be fixed for this release. |
| exist in CIMOperationRequestDispatcher but not in CIMConfig. The primary |
|
| ones to consider are: |
|
| a. System maxObjectCount. Setting some maximum size on what a pull |
|
| client can request (i.e. the maximum size of the maxObjectCount on |
|
| Open... and pull operations. |
|
| b. Pull interoperationTimeout (max times between operations). This is |
|
| the maximum number of seconds on the operationTimeout parameter of the |
|
| Open operations |
|
| c. Maximum size of the responseCache before it starts backing up |
|
| responses to the providers. |
|
| 5. Decision on EnumerationContext timeout (separate thread or just | 5. Decision on EnumerationContext timeout (separate thread or just |
| checks during other operations). Can we, in fact really keep the | checks during other operations). Can we, in fact really keep the |
| enumeration context table and queue under control without monitoring | enumeration context table and queue under control without monitoring |
|
|
|
| today | today |
| 6. Clean up code in Dispatcher. Want to at least reduce the code for the | 6. Clean up code in Dispatcher. Want to at least reduce the code for the |
| Open Operations to a set of templates so we know that the code is the | Open Operations to a set of templates so we know that the code is the |
| same for all operations. Right now the existing operations enum, assoc, |
same for all operations. Most of the common code for the enum, assoc, |
| etc. are all in templates but not the open operations. Note that the |
ref operations and their corresponding open/pull operations is now in a |
| |
set of template functions so that it is largely common code. Used the |
| |
templates where there is common code but not the same CIMMessage. However, |
| |
we should be able to do some of it with common functions (i.e. not templates) |
| |
by adding a layer to CIMMessage hiearchy and reduce code size. The |
| pull is a single template for both pullInstances and pullInstancePaths. | pull is a single template for both pullInstances and pullInstancePaths. |
| However, we might be able to reduce this to a single function by adding | However, we might be able to reduce this to a single function by adding |
| a new level to CIMMessage.h (CommonPullResponse) | a new level to CIMMessage.h (CommonPullResponse) |
|
|
|
| contains the pull data. Then we can use a single function to process all | contains the pull data. Then we can use a single function to process all |
| pull operations. | pull operations. |
| b. test the enumeration timeout thread | b. test the enumeration timeout thread |
| c. New Mergout to bring up to to date again. |
|
| d. Sort out issues with statisticalData since it really does not work | d. Sort out issues with statisticalData since it really does not work |
| with Open and Pull operations |
with Open and Pull operations. See separate bug 9786. |
| |
|
| |
30 September 2013 - CVS Update |
| |
Mergeout head of tree up to 29 September 2013. |
| | |
| 29 September 2013. CVS update. | 29 September 2013. CVS update. |
| 1. Modified calls to statisticalData.cpp to a) directly call with request | 1. Modified calls to statisticalData.cpp to a) directly call with request |
Return to
readme.pulloperations
CVS log
Up to [Pegasus] / pegasus