Aug 20, 2013, 3:21 PM
Hi Vladimir,
I understand what you are saying. I was trying to cache the config. so I can rebuild the grid using the config. However, it can not be done as well. As there is a serialization issue of caching the config back and forth. This is something that needs to be addressed (in my opinion). Because the ToConfig() call is a string. And I see no reason why it can not be cached.
Now, the reason why I am trying to cache the grid, because the config caching fails, and I have no other option. I am consulting this forum to give me an alternative to that since, as you have said, caching the actual control is a NO-NO. However, I have not acquired a definite solution to my issue. In my earlier post, it is clear that there is some problems with serializing the config back and forth and building the grid again. Even without caching, these lines does not work :
Thanks,
Allan
I understand what you are saying. I was trying to cache the config. so I can rebuild the grid using the config. However, it can not be done as well. As there is a serialization issue of caching the config back and forth. This is something that needs to be addressed (in my opinion). Because the ToConfig() call is a string. And I see no reason why it can not be cached.
Now, the reason why I am trying to cache the grid, because the config caching fails, and I have no other option. I am consulting this forum to give me an alternative to that since, as you have said, caching the actual control is a NO-NO. However, I have not acquired a definite solution to my issue. In my earlier post, it is clear that there is some problems with serializing the config back and forth and building the grid again. Even without caching, these lines does not work :
string config = gridPanel.ToConfig();
GridPanel newGrid = new GridPanel(GridPanel.Config(config));
ViewPort.Items.Add(newGrid);
There is no caching here. It is just plain serialization of the config. And it doesn't work. If this will work, then I can cache the string and my initial issue can be resolved. The solution of caching the control was a secondary alternative to this very first problem, which the support team acknowledges (see previous posts on this thread) but offered no solution.Thanks,
Allan