-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim
Kremens
Sent: Tuesday, June 27, 2006 5:39 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Re: loadvars vs xml onData
Why would that matter? I would assume that the loadvars and XML
objects would handle cached or no
ilto:[EMAIL PROTECTED] On Behalf Of Jim
Kremens
Sent: Tuesday, June 27, 2006 5:39 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Re: loadvars vs xml onData
Why would that matter? I would assume that the loadvars and XML
objects would handle cached or non cached files the same way, n
the cached file
--
T. Michael Keesey
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim
Kremens
Sent: Tuesday, June 27, 2006 5:39 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Re: loadvars vs xml onData
Why would that matter? I would assume that
ubject: Re: [Flashcoders] Re: loadvars vs xml onData
Why would that matter? I would assume that the loadvars and XML
objects would handle cached or non cached files the same way, no?
Jim Kremens
On 6/26/06, Steven Sacks | BLITZ <[EMAIL PROTECTED]> wrote:
> You're loading in a non-cached
Why would that matter? I would assume that the loadvars and XML
objects would handle cached or non cached files the same way, no?
Jim Kremens
On 6/26/06, Steven Sacks | BLITZ <[EMAIL PROTECTED]> wrote:
You're loading in a non-cached version each time right?
var myXml = new XML();
for (var a =
You're loading in a non-cached version each time right?
var myXml = new XML();
for (var a = 0; a < 30; a++) {
myXml.load(path + "?x=" + a);
}
BLITZ | Steven Sacks - 310-551-0200 x209
___
Flashcoders@chattyfig.figleaf.com
To change your subs
On Behalf Of Jim
Kremens
Sent: Monday, June 26, 2006 1:17 PM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Re: loadvars vs xml onData
Hi Stacey,
Check out the question:
"Anyone know why loadvars.onData gets results quicker than xml.onData"
He's comparing loadvars.onData
Subject: Re: [Flashcoders] Re: loadvars vs xml onData
Hi Stacey,
Check out the question:
"Anyone know why loadvars.onData gets results quicker than xml.onData"
He's comparing loadvars.onData with xml.onData - apples and apples, not
loadvars.onData with xml.onLoad.
It's a good qu
Caught on skimming
Intersting question now, I'm wondering which class has a higher overhead
file size wise...
> Hi Stacey,
>
> Check out the question:
>
> "Anyone know why loadvars.onData gets results quicker than xml.onData"
>
> He's comparing loadvars.onData with xml.onData - apples and apples,
Hi Stacey,
Check out the question:
"Anyone know why loadvars.onData gets results quicker than xml.onData"
He's comparing loadvars.onData with xml.onData - apples and apples, not
loadvars.onData with xml.onLoad.
It's a good question! I'd like to know
Jim Kremens
__
Its called first and is faster because its invoked as soon as you have
data, and before you actually parse or process the data. onData is always
gonna be called first. onLoad is called when the call has totally
completed, there fore at the end of the process, whereas onData is at the
beginning.
>
Hi,
I actually don´t know, but probably make more sense if the onLoad
method would be faster because it should be easier to parse the
LoadVars source rather than the xml one. But no idea why the onData
method is faster...
Sorry for not helping too much :S
Bye
On 6/26/06, Andreas Rønning <[EMAI
12 matches
Mail list logo
