Special Considerations for the SAP Textedit
Special Considerations for the SAP Textedit
Modified texts are always transferred synchronously to and from the frontend as a whole text. This means that, in a WAN, transfer times may be very long, regardless of the available bandwidth.
The worst-affected methods are those in which you pass tables as parameters. These are:
SET_TEXT_AS_STREAM SET_SELECTED_TEXT_AS_STREAM GET_TEXT_AS_STREAM GET_SELECTED_TEXT_AS_STREAM SET_TEXT_AS_R3TABLE SET_SELECTED_TEXT_AS_R3TABLE GET_TEXT_AS_R3TABLE GET_SELECTED_TEXT_AS_R3TABLEThe SAP Textedit uses an attribute cache, which stores information about whether the text has been modified, and the current line and column position. Reading these attributes therefore does not necessarily involve round trips to the frontend, since the relevant data is often available from the attribute cache. The call
CL_GUI_CFW=>FLUSH is still necessary, however, since you cannot tell as the user when the data from the cache is valid.