Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
DOT HISTORY will repeat itself
Message
From
19/10/2004 16:43:54
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., New Zealand
 
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
00950538
Message ID:
00952799
Views:
12
Rod,

re RVs: I must say I was interested that "experts" (not you) stated that SQL-injection protection in VFP was "extremely hard to architect into your app, and hardly ever seen in the wild", justifying a knowledgable article to educate the masses. As I pointed out, SQL-Injection protection has been widely used by VFP people since 1995. Those "useless" RVs are 100% immune to SQL injection. I was a little surprised that experts who routinely reject RVs on "technical" grounds seemed unaware of such an important technical fact.

I also asked you at the time whether an article would still appear (in Code magazine?) comparing VFP's inbuilt SQL-Injection protection with the clever ways you can achieve the same in dotNET. You did not answer, and I'm not holding my breath- your response at the time was to the effect of "gee, I didn't know that. Now, back to writing my Stored procedures" which presumably means you do not think it matters.

>>So in being fair.... John.... Did you ever look at paint.net or rssbandit. Were you correct on WInforms being slow performance wise?

OK, I decided to spend a few minutes on your paint.net example. First glitch: it doesn't work on win2000. Not pure dotNET, then. I wonder what it is PInvoking? But in the interests of progress: I accept your point, I'm sure these people have written a fantastic graphics package in dotNET.

However, I also seem to remember some fairly impressive graphics apps people wrote in VFP3 to celebrate the improved graphics functionality. That was interesting... but my tabbed entry forms still seemed to load slowly. I think most people here would understand exactly what I mean by that and would not argue "you're wrong, that graphics program works really well!"

Hopefully this makes it clear why I see no connection between paint.net and slow Winforms performance. We can agree to disagree.

>>I have to admit I was disappointed with your answer.

Sorry to hear it. I guess the difference is that you are editor of a magazine whose focus is on a tool designed for all sorts of development rather than the database apps that would occupy most people here. Presumably this is why you consider paint.net performace relevant and I don't. We can both be right, depending which forum/context we are in.

Regards

j.R
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us.
"
-- Shakespeare: Coriolanus, Act 1, scene 1
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform