-
Notifications
You must be signed in to change notification settings - Fork 34
Backport #378: PipeBlob as command's in/out #477
Conversation
881784c to
f02d10e
Compare
f02d10e to
b3bad64
Compare
b3bad64 to
4a62c8b
Compare
Ingvord
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| // Now, try to execute the command | ||
| // | ||
|
|
||
| //TODO extract class hierarchy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

| } | ||
|
|
||
|
|
||
| //TODO all command_inout methods must be moved to DeviceProxy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

| Except::throw_exception(API_PipeNoDataElement, "No data in pipe!", "DeviceProxy::write_pipe()"); | ||
| } | ||
|
|
||
| DevULong max, len; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

| // Prepare data sent to device | ||
| // | ||
|
|
||
| //TODO replace with createDevPipeData |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

|
As it is implemented it is not convenient to use the DevicePipeBlob. |


This PR backports #378 into tango-9-lts branch. Client may now use PipeBlob as command argument and server may return PipeBlob as command result.