Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Should dotNet become VFP?
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00917121
Message ID:
00917667
Vues:
38
>Case and point....web services. My guess is that 1 tenth of 1 percent of all >Fox developers ever made serious use of that feature - which was really a >feature of SOAP - not Fox.
>
>It is interesting to watch where people try to hang their hat and claim >victory.

Actually - I am a developer who thinks VFP is a great tool for what it is good at (along with .NET and other tools/technologies) but think that the VFP implementation of web services is severely limited.

I have had to interface a java web app with a vfp system via web services. The fact that VFP doesn't handle complex types and thus needs to work with encoded strings for parameters/returns is ugly. Not (a) supporting complex data types and (b) therefore not being able to serialize them (or even vfp objects) means that VFP is great at using web services to communicate with VFP but not much else.

I guess the upside is that you get to know the MS XML DOM inside & out :)
Cheers,
Jamie
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform