WsDfu/ListHistory & WsDfu/EraseHistory to return a valid U/I response
Description
The ESP services WsDfu/ListHistory WsDfu/EraseHistory
are returning a response in de-serialized binary data format. Please add a xml/json compatible response format i.e. <History></History> so that we can display to the user in a readable format. It would be fine to return the binary data just in a different element.
Looked over Attila's current pull request for this issue. Tony will likely ask for several changes including capitalizing the FileHistory children names, but the overall structure looks reasonable and not likely to change. Here's my interpretation of the response you can expect: <History> <FileHistory> <originName></originName> <originOperation></originOperation> <originTimestamp></originTimestamp> <originIP></originIP> <originPath></originPath> <originOwner></originOwner> <originWorkunit></originWorkunit> </FileHistory> ... <FileHistory> <originName></originName> <originOperation></originOperation> <originTimestamp></originTimestamp> <originIP></originIP> <originPath></originPath> <originOwner></originOwner> <originWorkunit></originWorkunit> </FileHistory> </History>
Miguel Vazquez April 12, 2017 at 8:26 PM
If we want to make the history a xml type view then we need to return a xml BLOB. FYI.
Attila Vamos April 12, 2017 at 4:49 PM
Copied from Flowdock discussion:
Miguel Vazquez April 12, 2017 at 4:37 PM
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The ESP services
WsDfu/ListHistory
WsDfu/EraseHistory
are returning a response in de-serialized binary data format. Please add a xml/json compatible response format i.e. <History></History> so that we can display to the user in a readable format. It would be fine to return the binary data just in a different element.