Hi Ramil,
Thank you very much for your input!
>Hi Dmitry,
>
>Based on our implementations, I would recommend that you stay away from using objects to hold data. This decision becomes very critical when you get to 100MB+ data objects. And if you intend to hold these objects in a collection, then you're even more in dire straits. We basically hold what would be comparable to the DataSet class in .Net in memory and it is literally killing our application. We had to write code to clear the memory buffer. Performance is not optimized as well.
>
>Data objects are very useful when used in small sizes. One of the beauties of an object is that you can reference them elegantly compared to arrays (ie. objProduct.ProductId compared to aProducts[1,1]).
>
>Again, this is just based on our implementations.
>
>
>>Hi,
>>
>>I am using arrays as way to pass the information from UI to BIZ/DA objects but thinking about changing to objects (using SCATTER/GATHER). In terms of memory use, do objects require more memory?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
