Servlet, and likely slower than a comparable JSP page. The actual time
difference would greatly depend on the specific setup you're using. Nothing
against the language, that's just the tradeoff you make for the extra
niceties that CF provides.
The reason is greatly due to scoping of variables. CF is typeless, but Java
isn't. Thus if you're using actual Java (JSP, Servlets), you the runtime
engine doesn't have to go through an AMAZING about of hoops to get a
variable that you can interact with. I'd love to see CF grow an option to
use strong typing, but I don't know how much of a pipe dream that is.
Just to be clear, I'm not saying CF doesn't have suitable performance for
building web applications. Much the contrary. It does an amazing job at
still running fast, even though it does a huge amount of work behind the
scenes to make things easier on the developer. It's just not the fastest
you're going to find.
Cheers,
barneyb
> -----Original Message-----
> From: Calvin Ward [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 29, 2004 4:40 AM
> To: CF-Talk
> Subject: RE: How does CF generated Java bytecode compare with
> Native Java ytecode
>
> It is slow compared to what and by how much?
>
> -----Original Message-----
> From: Barney Boisvert
> Date: 6/28/04 8:12 pm
> To: CF-Talk
> Subj: RE: How does CF generated Java bytecode compare with
> Native Java bytecode
>
>
>
> <heresy>If you want a fast application server, don't use CF,
> pick something
> else.</heresy>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
