on 12-22-2005 11:37 AM
Hi,
Is there any difference (performance-wise only), between storing table data in the View context directly, or storing it in the controller's context , and mapping the controller context nodes to the view's ones.
Provided that we add table rows to a context with something like:
wdContext.nodeX().addElement(wdContext.nodeX().createElement(iterator.next()));
Thanks in advance.
Regards,
Angel
hi angel,
storing value attribute in the view context in local data(local scope). storing value attribute in controller context is global data(global value).If u map the view context to the comp. controller u can use this data in another view
for table first u store data in value a
ex:
String place=wdContext.currentContextElement().getPlace();
String sex=wdContext.currentContextElement().getSex();
IPrivateTablleview1.IMynodeElement x=wdContext.nodeMynode().createMynodeElement();//this for creating element for the node
wdContext.nodeMynode().addElement(x);//this is for adding element to the node
wdContext.currentMynodeElement().setPlace(place);//this for setting data to the element
wdContext.currentMynodeElement().setSex(sex);
wdContext.nodeMynode().moveNext();
hope this helps u,
Regards,
Arun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Arun,
Thanks for the reply, but as i said before, I don't care about the scope/visibility of the data - only about if there is any speed difference between the two ways. For example -> is the same data transmitted to the client depending on the context, in which the data is stored? (view context, controller context, etc.)
Regards,
Angel
Message was edited by: Angel Todorov
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.