(file) Return to readme.pulloperations CVS log (file) (dir) Up to [Pegasus] / pegasus

Diff for /pegasus/readme.pulloperations between version 1.1.2.27 and 1.1.2.30

version 1.1.2.27, 2014/04/28 00:52:28 version 1.1.2.30, 2014/05/04 23:05:10
Line 11 
Line 11 
    1. Binary operation from OOP.  Need to add counter to binary    1. Binary operation from OOP.  Need to add counter to binary
       protocol to be able to count objects in response. Generates       protocol to be able to count objects in response. Generates
       warnings in things like messageserializer and does not work with       warnings in things like messageserializer and does not work with
       OOP right now.  Corrected by converting to XML.        OOP right now.  Fixed by converting to XML.
    2. OpenExecQuery - Code is incomplete in that it does not include the    2. OpenExecQuery - Code is incomplete in that it does not include the
       return from the exec query function to the aggregator yet.       return from the exec query function to the aggregator yet.
    3. Code for Pull part of OpenQueryInstancesRequest a) should be part of    3. Code for Pull part of OpenQueryInstancesRequest a) should be part of
Line 23 
Line 23 
    4. External runtime variables. Proposing that they be fixed for this release    4. External runtime variables. Proposing that they be fixed for this release
       rather than set by configuration.  This should be discussed.  Am making       rather than set by configuration.  This should be discussed.  Am making
       this a separate bug.  See bug 9819 for the changes to cover this.       this a separate bug.  See bug 9819 for the changes to cover this.
    5. Consider moving some more of the code in dispatcher from templates to     5. Move processPull code in dispatcher from template to
       common functions which would mean adding intermediate classes in        common function which would mean adding intermediate classes in
       CIMMessage but would reduce code size. Currently the change that        CIMMessage but would reduce code size. This createsCIMmessage
       we should make for this is to create a new message CIMPullRequestData...        CIMPullRequestData... between CIMRequestDataMessage and the Pull requests
       between CIMRequestDataMessage and the Pull requests since they all        since they all have exactly the same input and output pararameters.
       have exactly the same input and output pararameters (The  
       CIMResponseData hides the response object differences)  
    6. Extension to avoid double move of objects in CIMResponseData (one    6. Extension to avoid double move of objects in CIMResponseData (one
       into enumerationContext queue and second to new cimResponseData for       into enumerationContext queue and second to new cimResponseData for
       response.  Want to avoid second move by extending Open/Pull response       response.  Want to avoid second move by extending Open/Pull response
       messages to include count and CIMResponse data to count objects out       messages to include count and CIMResponse data to count objects out
       of queue when converting (avoids the second move). This would mean       of queue when converting (avoids the second move). This would mean
       extending the output writers to allow the count field to be supplied       extending the output writers to allow the count field to be supplied
       so they would only create output for up to the count supplied.        so they would only create output for up to the count supplied.(Make
    9. Add more static tests (currently only OpenEnumerateInstances is covered).        this future beyond bug 9676)
      9. Add more static tests (currently only OpenEnumerateInstances and
         OpenEnumerateInstanceNames covered).
       Low priority because most of this except exact XML covered in other       Low priority because most of this except exact XML covered in other
       tests.  ADDED OpenEnumerateInstanceNames        tests. note that we can only add very limited tests since a) no
         way to test multiple opertions in sequence(i.e. open/pull) and
         cannot be sure how many responses will come back in all cases even
         for open.
    10. Could clean up the CIMOperationRequestDecoder.cpp rejectCIMException    10. Could clean up the CIMOperationRequestDecoder.cpp rejectCIMException
       further since there is some overlap.  That is low priority.        further since there is some overlap.  Low priority.
    12.Add exception for to many entries in EnumerationContextTable. The     11.Correct issue between operations and HTTP where we are sending
       test exists but is ignored right now.  
    12. Correct issue between operations and HTTP where we are sending  
       trailers with exceptions.  Also correct issue where we are       trailers with exceptions.  Also correct issue where we are
       sending endOfSequence and EnumerationContext in response when       sending endOfSequence and EnumerationContext in response when
       we send CIMException.  DONE        we send CIMException.  DONE Except that we really need to get
         rid of the trailers completely for pull operations.  Need to
         have flag to send as non trailer (probably non_chunked flag)
      12.Make enumContextTable hashtable dynamic and create entirely within
         CIMOperationRequestDispatcher.cpp. Today it has a static size
  
    NEXT TASKS:    NEXT TASKS:
       b. Finish and test the OpenQueryInstances       b. Finish and test the OpenQueryInstances
Line 58 
Line 63 
          timeout thread) and a place where not mutuxed, primarily the          timeout thread) and a place where not mutuxed, primarily the
          timeout thread.          timeout thread.
  
   4 May 2014
   1. Clean interface with EnumerationContext timeout thread
   2. Remove more diagnostics
   3. Correct issue with enumerationContext Release that was causing
      failures during nightly tests.
   
   2 May 2014
   1. Remove Diagnostics from ResponseData.cpp
   2. Correct setup and start of EnumerationContextTimerThread
   3. Change limit on max number of enum contexts to be set from Dispatcher.
   4. Increase size of hashtable for enum contexts.
   5. Corrected issue causing failures in removeContext. Now runs through nightly
      tests most of the time.
   1 May 2014
   1. Cleanup of code and variable names.
   2. Removed namespace variable from EnumerationContext.  It was never used.
   3. Added test for max number of open enumerations.  Right now it is fixed
      and set about 100. Note that this is tied to the size of hash table
      so that there is a issue with more dynamic setting of max and the
      hash table size.
   4. Removed several unused functions.
   5. Found one possible issue causing thread conflict but not the core one
      yet.
   
   30 April
   1. Added exception response to dispatcher for Limits exceeded on
      CreateEnumerationContext. Returns Exceeded server limits CIMException.
   2. Fixed possible deadlock where we were not unlocking EnumerationContext
      under error condition
   
   
 27 April - mergeout to head of tree 27 April - mergeout to head of tree
 1. Mergeout of the code to the head of tree. Documented that mergeout in 1. Mergeout of the code to the head of tree. Documented that mergeout in
    the bug    the bug

Legend:
Removed from v.1.1.2.27  
changed lines
  Added in v.1.1.2.30
No CVS admin address has been configured
 Powered by
ViewCVS 0.9.2