Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Threads
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00967880
Message ID:
00968514
Vues:
8
It's important to understand for setup reasons, but, to say it is not multi-threaded generally, I think, is causing more confusion than helping. Like I said, regardless of how it gets there, it is still running multiple threads at the same time (which is a very good thing!).
VFP mtdlls are not "free-threaded" and I don't think anybody ever claimed they were. Free-threading, like what's available in .NET, is probably more efficient, but also more dangerous. The slight performance hit you describe will probably never be noticeable to anyone when calling a vfp mtdll from ASP.NET(see http://www.activevfp.com/avfpdemo2/default.aspx). I think your own performance tests actually showed VFP mtdlls performing better when called from ASP.NET in COM+. In fact, at this point, VFP mtdlls are the best we can do with VFP and multithreading things like web apps, so, why attack it??

>>Sorry, for most intents and purposes vfp multi-threaded dlls(mtdlls) are indeed multithreaded(thus the name). Multiple threads are running at the same time. The technology behind it doesn't really matter as far as this is concerned...
>
>Oh, but it does!
>
>In fact, if you don't understand how this works you can get into serious trouble very quickly.
>
>For example, try setting up an ASP.NET page without setting ASPCOMPAT="true" and you can see just how multi-threaded a VFP COM object is. Without ASPCOMPAT ASP.NET will create your VFP COM object on a true freethreaded (MTA) thread and your objects will blow up at worst or do all sorts of crazy stuff when they are running simultaneously at best.
>
>MTDLLs are a simulation of multi-threading and really the COM system provides this for you. VFP can play by STA rules. It's important to understand this with ASP.NET for example. The STA imposition on VFP MTDLLs in fact is one of the reasons why ASP.NET is much slower in calling VFP COM objects than classic ASP was for example.
>
>It works, but it's important that one understands what's actually happens behind the scenes lest you get into trouble and not have any idea why things are going wrong...
>
>+++ Rick ---
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform