Matthew Pearson wrote:
We are currently using PHP to build a set of web pages to interface to MySQL, but it is likely that it will have to talk to some legacy databases. Is PHP likely to be able to do that or is it SQL only for DB support?
PHP can pretty much do anything! What sort of legacy DB are you thinking of?
Is JavaServlets a better way to go than PHP? I've done some (don't stone me for this) ASP.Net with C# in the past for web pages and that was very easy to put together good web-interfaces, but the produced web-pages can get massive without care being taken.
Personally, I'd say if you're part way there with PHP stick with it unless you have to change. Without knowing what DB you're needing to access its hard to know whether the need to change will arise, though.
Is anyone doing web-page/framework stuff in non-interpreted languages (perhaps for reasons of speed of execution?) and is this even likely to be necessary? (I know that depends a lot on what exactly you are doing, but some stories would be good.)
I doubt that it is necessary; there are some very big DB-based apps running PHP (or Perl/Python/etc) without problem. If you feel the need, look at the various PHP accelerators which cache the compiled byte code; they can make a big difference if that interpretation time is your bottleneck. I suspect that the DB access will be the bottleneck, though. Before you start optimising, I'd suggest profiling your application to see where the weak points are.
-- Mark Rogers More Solutions Ltd :: 0845 45 89 555 _______________________________________________ Peterboro mailing list [email protected] http://mailman.lug.org.uk/mailman/listinfo/peterboro
