The company I work for has done a lot of stuff with ASP and they want to use
Java based technologies for all projects moving forward. One of the reasons
is that they feel that their ASP code (which I've never worked on or seen)
is completely unmaintainable and is write-only. New developers have a
really hard time understanding it, and it's hard not to replicate code
through many pages, making changes to that code really annoying. I don't
know much about ASP, but this is something my boss told me about their ASP
projects.
jeb.
----- Original Message -----
From: Patrick Saunders <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 20, 2001 8:10 PM
Subject: ASP v Turbine
> Hi all,
> I'm pretty annoyed, I sent a large, detailed question
> about how Turbine compares to ASP and
> the mail server ate it (ie didn't get to Turbine list).
> :(((
>
> Anyway, the crux of my question was:
> What are the techincal pros/cons of Turbine(Velocity) V ASP ?
>
> I've got some ASP webbies trying to hijack control of a
> web project I'm working on and I'm pretty pissed,
> though I need to go in with some decent ammunition
> as to what regards Turbine/Velocity is superior.
>
> The web site is a fairly straight forward Financial
> analysis site, that allows users to put in ASX (company)
> codes and view charts (Kavacharts is used for the charts).
> It is expected the site will be popular, so many hundreds
> of users are possible.
>
> The web designers have been using Applets to generate the charts
> and I think this in itself is bad, surely images are more browser
friendly?
>
>
> All comments welcome,
>
> Thankyou,
>
> Patrick Saunders.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
