Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Should dotNet become VFP?
Message
De
30/06/2004 01:42:20
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., Nouvelle Zélande
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00917121
Message ID:
00918862
Vues:
37
Dear JVP,

Lets just assume that I followed your advice and have read up about dotNET security in concord with your assumption that I knew nothing about it ;-)

I need to know whether you are referring to dotNET's Code Access Security, or database access methods, or level of obfuscation to prevent decompilation, or whether you have some cool advice about using assert safely, or what.

It matters, because quite a few of the dotNET security drum-rolls are less relevant for those writing browser apps, which according to the experts is most of us. Serving HTML from behind a SPI "port 443"-forwarding firewall and/or a Linux proxy means you can be fairly pragmatic about internal security. But other concerns such as SQL injection are much more relevant. IMHO, anyway.

So where do you want to start? Lets have a calm, rational, technical discussion about security.

No compulsion, but how about we start here: CAS is absolutely fascinating in dotNET- I give it a 10/10 cool rating. But where do you think it will provide a compelling proposition for VFP people?

Regards

JR
"... 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
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform