I understand what you are saying ... and yes, while OpenBD does not
compile directly to byte code per se, it does indeed go through an
internal compilation. This is where "interpreted" gets misused a lot,
usually by those trying to labor a point that it is slower.
OpenBD does compile your template upon first load, removing all the
unnecessary fluff and organizing things in a manner that when we handle
the request it is as fast as possible. Every request that comes in,
does NOT incur this overhead and you are running against our internal
representation of the page/cfc.
We have highly optimized this process over the 12years we've been doing
this, to take advantage of how people execute requests and to optimize
memory usage. This is how we scale to extremely large loads more
efficiently than other alternatives. We've always designed for the
large floods, not the trickles.
On 11/08/2012 03:47, Confused wrote:
I'm not interested in hiding my source. Good luck to the moron that
steals my code. Let me know how that 1st update worked out. :)
I was just interested in the pre-compiling part for faster execution.
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
