> > Paolo > > PS Unless a future upgrade recognises this performance issue and we have > another window of opportunity we will not be upgrading for a very long time. > It seems that Macromedia have been so obsessed with competing for all round > integration they have forgotten what they are here for - to chuck out some > HTML. If this is the direction Macromedia are now going, although very > reluctantly, we might end of ditching CF, at least for some projects. CFMX > is a second-class web application. I seem to remember a company by the name > of Netscape that went down a similar road.
I am really sorry to hear you say this... I am tempted to say something really smart arsed here but I am not going to. We do try hard to make CF the best it can be but we need customers to help us out here. This is why we have methods to help out people like yourself. Having be involved in quite a few large CF 5, CFMX and even spectra projects I know just how critical performance can be to an application an how one sould go about testing and tuning servers for performance. Pressing F5 is not a performance test Even looking at the debug output is not a true measure of performance, unless you really know what you are looking at. Ever wonder why some very fast code will often come back a 0ms one time and 10ms the next time on windows? It is not a limit of CF (mx or 5) it is a limitation of the OS, windows can not work out the difference... I am quite disappointed that you consider our product second class, maybe you will have more luck with ASP.NET L. -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
