View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008341 | 10000-014: PubSub | Spec | public | 2022-09-21 13:01 | 2022-09-23 14:54 |
Reporter | Matthias Damm | Assigned To | Matthias Damm | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 1.05.01 | ||||
Target Version | 1.05.02 | Fixed in Version | 1.05.02 | ||
Summary | 0008341: Allowed open modes for PubSubConfigurationType | ||||
Description | Current definition for PubSubConfigurationType: Requirement from FX WG: Problem: Solution: The third mode needs some special handling if you read and write. E.g. open for Read + Write, Read the old configuration, SetPosition to beginning, write new configuration, call CloseAndUpdate. If the new configuration is smaller than the old configuration, the buffer would theoretically contain parts of the old configuration but the way of handing CloseAndUpdate would not have a problem since the content of the buffer would be read by the decoder only until the valid new part. | ||||
Additional Information | An additional point, | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
agreed to add this to the 1.05.02 release (post RC edits). |
|
In 9.1.3.7.1 PubSubConfigurationType Replaced When a Client opens the file for writing the Server will not actually update the PubSub configuration until the CloseAndUpdate Method is called. Simply calling Close will discard the updates. With When a Client opens the file for writing the Server will not actually update the PubSub configuration until the CloseAndUpdate Method is called. Simply calling Close will discard the updates. Open for writing is an exclusive access. Clients shall open with Write flag set only for the execution of the sequence of Method calls necessary for a configuration update. When a Client opens the file for reading and writing, the Client shall follow the following steps.
The Read + Write (0x03) option allows a Client to ensure that the changes are consistent with the current configuration and to avoid that another Client made changes between read and write. |
|
Agreed to changes edited in F2F meeting. |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-09-21 13:01 | Matthias Damm | New Issue | |
2022-09-21 13:01 | Matthias Damm | Status | new => assigned |
2022-09-21 13:01 | Matthias Damm | Assigned To | => Matthias Damm |
2022-09-21 14:41 | Jim Luth | Note Added: 0017751 | |
2022-09-22 15:50 | Matthias Damm | Status | assigned => resolved |
2022-09-22 15:50 | Matthias Damm | Resolution | open => fixed |
2022-09-22 15:50 | Matthias Damm | Fixed in Version | => 1.05.02 |
2022-09-22 15:50 | Matthias Damm | Note Added: 0017804 | |
2022-09-23 14:54 | Jim Luth | Status | resolved => closed |
2022-09-23 14:54 | Jim Luth | Note Added: 0017839 |