G'day all,
I will quickly summarise my situation.
I have been building a Turbine based app for the last
few months. It is currently using Mysql based on a Linux machine.
It's a relatively simple Financial web site that generates
charts and reports based on ASX (Australian stock Xchange)
codes. ie you put company (ASX) codes and some other criteria
in and you get a report and/or charts.
I have Mysql as the database, which stores around 30Mb of data.
There is no other site like this in Australia, and my client
envisages that it will be very successful and heavily used, with perhaps at
least a 200 or more users accessing the site at once.
Now, the issue is that there is another company which is doing the
front-end design. They have traditionally been ASP-centric and the dude
that does the pages has started griping this and that about velocity, though
I think it's because it hurts his head to much to try and understand
and therefore just easier to criticise (He started complaining about
not much documention for Velocity - my heart bled).
Anway, they've hacked up a couple of screens in ASP to show
the client (who isnt' a techo so can't judge ASPvTurbine), and
basically saying "Hey, this works, what do we need this Turbine stuff for??".
I've tried to explain some of the advantages of of Turbine , ie logging,
connection pooling, scalability, caching pages etc, but I don't
have enough knowledge about ASP to say with 100% certainty
where Turbine kicks its bum or vice-versa.
I would be indebted if people could give objectively as many pros/cons
concering ASPv Turbine (Using Velocity).
It goes without saying that there is a certain amount of honour on my part
involved in this too; that I admit, nor do I want to see another site using M$
products.
Regards to all,
Patrick Saunders.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
