One more point about this. It is the scripting language that is a
performance hit, and is designed for humans. For example, think of all
the "lookups" that must be performed with witango tags, even if you are
a compulsive scoper like I am. The witango server must parse the result
of each tag from the inside out. Especially when dynamic referencing is
done. When I look at some of my tafs, I wonder how the server can parse
all that as quickly as it does. Also, tango has to look at the contents
of each variable and determine how to treat it. That must take a huge
hit. For instance, think of the logic to determine what to do with the
contents of a variable local$foo if the contenst are "0.44". At times,
witango treats this like a string, and at times, it treats it like as a
floating point number. Now what if the value is "$ 10.49". It now has
to look up money formatting to determine if this should be treated as a
floating point number and there allow math manipulation. Not only that,
but you can have a variable local$foo, and assign a string value to it
at one time, and a number at another, and perform calcs on it, and
Witango won't bark at you at all. As humans, it is easy for us, we just
code it and the server figures out the rest, but that is a lot of logic
for the server to work through at any given moment. Especially when we
are looping through this kind of stuff.
I imagine witango would gain a significant performance increase if we
were required to "type" variables prior to using them. The drawback
would be that if you type local$foo as an integer, it will only accept
whole numbers. If you try to assign a string, it will be "0", and if
you assign 1.44, it will be "1". If you type local$foo as a string and
assign "222.44", you won't be able to perform calcs on it without a
conversion.
I am not sure how old code would work, which is probably why witango
has not implemented this.
Robert.
On Monday, June 30, 2003, at 08:09 PM, Atrix Wolfe wrote:
makes sense to us, however to reference an apple, it would have to go
through a whole bunch of lookups just to get to the data it needs. If
you
could see your computer working inside somehow it would be jumping all
around in RAM just to get to one spot that it could have gotten to much
quicker if it went straight there, not to mention all the memory
overhead to
store all the lookup tables.
--
Robert Garcia
President - BigHead Technology
CTO - eventpix.com
2781 N Carlmont Pl
Simi Valley, Ca 93065
ph: 805.522.8577 - cell: 805.501.1390
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/ - http://theradmac.com/
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
