Re: Witango-Talk: Boosting Server Performance, and TCFs

[Robert Garcia]

Just because our tafs would be compiled in some native format, doesn't 
mean we would have to start worrying about things garbage collection. 
The compiled tcf would would have in/out points and process data 
within. It would run within the memory space of the witango server, and 
the server would handle the garbage collection and the nasty stuff. The 
main benefit would be that complex methods in a tcf would not be 
scripted, but compiled so that there would be no tag processing and the 
other performance drags that are inherant with an interpreted language. 
It would mean, though, that certain things you can do in a tml or taf, 
you could not do, like dynamic referencing.

Robert.

On Tuesday, July 1, 2003, at 09:49  AM, Scott Cadillac wrote:

But it does add several layers of complexity too. I'm not an expert at 
this
level by any means, but it seams to me that Witango isn't ready to 
support
this kind of low-level environment (nor any interpreted language for 
that
matter, e.g., ColdFusion).

For example, garbage collection and other memory allocation issues - 
what
sort of Metatags would we need for this?
--

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