Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Background process
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00584685
Message ID:
00638630
Vues:
29
I'm mixing things now, since you're interested. :)

I built my data-processing object as a subclass of the Timer object (Define Class Processor as Timer OLEPUBLIC), made that .prg into a MTDLL, and put that into a COM+ server package. I then tried the same kind of multi-user banging that I did on the Pool Manager sample, and it didn't break. So far. :)

As long as I stick with the subclass of the Timer for my custom data-manip object, I get the best of both worlds because the object auto-yields to other processes, but the calling VFP .exe doesn't have to wait for it to synchronously return.... Is that right?

I have a side-question: When an object is instanced, is there any way for it to know what it's name is? I want to save a textlog named after the object reference, but right now since all objects have the same name, the log gets stomped on by everything else.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform