You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@plc4x.apache.org by "César García (Jira)" <ji...@apache.org> on 2020/03/04 18:53:00 UTC

[jira] [Commented] (PLC4X-182) Request split / Message Split

    [ https://issues.apache.org/jira/browse/PLC4X-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051525#comment-17051525 ] 

César García commented on PLC4X-182:
------------------------------------

Hi,

1. The modification made to the driver allows the partition of the items by item size and regrouped according to the size of the PDU.
2. Part of the code for handling long messages was transformed into a Netty layer, only dedicated to executing point 1.
3. Bits fix requests are made as individual Items, but the partition is made from the beginning. This makes it easier for each layer in Netty to do only one thing.

The result of this can be seen in the attached capture in the PLC4X-181 activity.

For version 0.6.1, very long Items (that exceed a PDU) both write and read will be rejected indicating poor quality.

Waiting for your observations,

Best regards,

> Request split / Message Split
> -----------------------------
>
>                 Key: PLC4X-182
>                 URL: https://issues.apache.org/jira/browse/PLC4X-182
>             Project: Apache PLC4X
>          Issue Type: Improvement
>          Components: Driver-S7
>            Reporter: César García
>            Assignee: César García
>            Priority: Major
>             Fix For: 0.6.1
>
>
> # A request with many Items is divided within the limits allowed by the size of the PDU.
>  # If one of the requested Items exceeds the size of the PDU it is trimmed to the maximum size of the PDU. The existing code tries to split the message, but it fails. This generates an unsafe condition.
>  # Rethink the routine for handling long messages, as an additional layer in Netty.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)