Skip to Content
0
Former Member
Mar 18, 2009 at 08:35 PM

Web Dynpro context Best Practices

52 Views

Hello Experts,

While i am going through the Best Practices for optimizing web Dynpro applicaion performance document provided by SAP,there is a point which talks about best practices for Web Dynpro contexts while using ARFC models.

the point is :Donu2018t Declare Context Model Nodes and Attri- butes NOT used for Data Binding Purposes.

Further explanation for this point is:

When model data retrieved via backend connections (Adaptive RFC, Web Service, EJB) has NOT to be transferred to the user interface via data binding:

��There is no need to declare context model nodes and attributes bound to model classes and attributes for storing business data in the context.

��Just programmatically operate on model objects directly to access model data in your controller classes

By omitting the definition of a context-to-model binding relation in a controller context, the generated context interfaces are kept as slim as possible, and this reduces the permanent memory space* on server side.

Can some body explains what exactly meaning of this Best practice?

Futher to this Best Practice,i want am looking for some suggestions in my current scenario.

In Our application we have model nodes created for each RFC and we do have Value nodes which are similar to model nodes.After RFC FM is executed ,data from model nodes are copied to value nodes with some processing and these values nodes are used throughout the application.Now my webdynpro context is holding similar data with some changes in two context nodes(Model and Value).I want some suggestion on reducing memory consumption.

Thanks in Adavance.

Regards,

Balaram Naidu