Object Orientation in arrays

[xavier.bury at clearstream.com]

David,

The thing with XUL or the basis for this question is to just translate XML 
type data or streams of data
to memory for faster management.... 

I also tried to work with xml in a recent project and as soon as i had 500 
objects in this text variable
things started slowing down drastically... Which is what i would like to 
avoid.

Since puting arrays into arrays is out of the question in rev (though it 
would be idea), and XML does 
require a bit more parsing than arrays, there must be an easier, or more 
efficient method...

BTW, i did try xml into an array, and the problem is still parsing xml... 
Parsing Arrays is much more
efficient...

Thanks for the comments

cheers
Xavier

use-revolution-bounces at lists.runrev.com wrote on 22/11/2005 12:16:24:

> On 22 Nov 2005, at 08:53, xavier.bury at clearstream.com wrote:
> 
> > I know how to handle these, that's not the problem. Im wondering if 
> > there
> > isn't
> > a better way to handle the arrays and/or which is easier to manage...
> 
> Not with arrays - I don't think they are up to handling the complex 
> nesting required. Think you have to work with XML directly for all 
> but the simplest configurations.




-----------------------------------------
To make communications with Clearstream easier, Clearstream has
recently changed the email address format to conform with industry
standards. The new format is 'firstname.familyname at clearstream.com'.

Visit us at http://www.clearstream.com

IMPORTANT MESSAGE

Internet communications are not secure and therefore Clearstream
International does not accept legal responsibility for the contents of
this message.

The information contained in this e-mail is confidential and may be
legally privileged. It is intended solely for the addressee. If you are
not the intended recipient, any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful. Any views expressed in this e-mail are
those of the individual sender, except where the sender specifically
states them to be the views of Clearstream International or of any of
its affiliates or subsidiaries.

END OF DISCLAIMER